yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] b1g1an:
I tried the same and am happy to say its now back to its old self HOWEVER Play Music is still borked, is it OK just to reflash GApps over the top?
[Xoom Android Development] sigfridov:
I have the same issue.

Today I charged the tablet but using the dock, so this started with 23% of charge and showing a white Led color. When charge finish getting close to 100% (92% +-) it changed to green.

How may I to setup this feature?

Thanks in advance.
[Xoom Android Development] John.Spence1:
So, just so I have this right..

1) Download all required zip files to external SD card.

2) Flash TWRP zip. Reboot Recovery.

3) Repartition with TWRP recovery.

4) Flash Rom zip

5) Flash Gapps zip

6) Flash SU zip

7) Reboot system. Wait for it to come up, and working okay.

8) Flash photosphere, and V3 zips.

9) Configure OC and SD read as needed.

That is correct, right?

John
[Xoom Android Development] sigfridov:
Which Recovery Version?

Did you use this recovery:

http://d-h.st/nmP

The recovery is an special version specially developed to be used on BigPart process.

Did you?
[Xoom Android Development] John.Spence1:
I downloaded the one in the OP...
[Xoom Android Development] sigfridov:
Data have to beformated

Did you follow step by step the BigPart instructions?

I mean Source like this:

Repartition Guide

1) Your data will be totally wiped! If you have Nandroids, TitaniumBackups, or anything of any value on your internal storage, copy them to your microsd or computer! They will be gone forever! Your microsd card is the only safe haven on your Xoom during this process.

2) Put all needed resources on your microsd card! You will need the original TWRP 2.6.3.0 touch recovery from [MENTION=3900214]runandhide05[/MENTION], TWRP 2.6.3.0 BigPart version, your desired rom, and the BigPart boot image that goes with your desired rom. The BigPart boot images can be found in the next section.

3) Reboot into recovery. Flash TWRP BigPart. Don't reboot just yet.

4) Go back into wipe menu and wipe everything but /sdcard.

5) Go to reboot menu and reboot into recovery. Disregard the "No OS" warning and don't install SuperSU when asked.

6) When you come back into recovery, it will think your data is encrypted but it's not. Go into wipe menu and "format data". Type "yes" when prompted. When done, go back into wipe menu. Select "Advanced Wipe". Check "system" and "cache" and wipe them.

7) Hit Home then go to reboot menu and reboot recovery. Once again, disregard "No OS" warning and don't install SuperSU when asked

8) When you come back into recovery, go into mount menu. You should see "cache" and "data" checked. "System" will be unchecked. Check it to confirm it mounts, then uncheck it. Congratulations! You are now repartitioned!

9) Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". Flash your rom, BigPart boot image package, and any other resources as you normally would.

10) Reboot into system. You are done!

You should follow it up to number 9, then instead to flash a boot.IMG, you have to flash Omni ROM an restart as you mention in your step 4) above.

The rest of step noted by you are correct.

Try to check md5sum for all downloads files, because if they are corrupted no way to succeed with the installation .

I have already deleted both instrucctions wich produce misunderstanding for BigPart process. I mean, this OMNI ROM no need additional boot.img, it is all included, so you need, then in the step 9) above you need to flash:

ROM

GAPPS

SU_Update

Other

Good luck
[Xoom Android Development] kmcrane:
For the last 8 months I was on eos 3 stable.. Then i saw this thread and was excited. I use omni on my Gnex!

How is multi user in this with the xoom? I know that a long time ago when on eos it was kind of buggy. My wife would like that option again.

And it saves me from buying her, her own tablet. :p
[Xoom Android Development] notbrodie:
non-existant

Sent from my Nexus 5
[Xoom Android Development] Vnvjeep:
I was on EOS 4 for the longest time until saw this... I immediately jumped over, and haven't had ANY regrets. It's actually snappier than EOS believe it or not. I'm absolutely loving it.

-Mike
[Xoom Android Development] kmcrane:
Ok.. I saw it in the settings, but it's fine. I am so happy to play with my xoom again..
[Xoom Android Development] rmcsc:
I'm getting stuck at bootloader. What am I missing here?
[Xoom Android Development] notbrodie:
I read multi-window, my bad. I don't know about multi-user...

Sent from my Nexus 5

---------- Post added at 07:51 PM ---------- Previous post was at 07:50 PM ----------

following the directions, most likely?

Sent from my Nexus 5
[Xoom Android Development] kentedman:
Reflash the rom but do not flash the boot.img
[Xoom Android Development] kmcrane:
Do we only flash the gapps in the OP? or can we flash banks gasps, or newer PA gapps like the 1-17-14?
[Xoom Android Development] drewski_1:
I use current PA GApps
[Xoom Android Development] huckl3b3rry:
Don't know about a video but I will recommend that you follow the instructions from the bigPart recovery thread. I used the instruction in this thread and screwed it up but was able to fix it. Maybe you aren't as dumb as I am :). If you follow those instruction its pretty easy.
[Xoom Android Development] kmcrane:
Do you use full modular or the full stock ones? I use the full stock on my phone, but OP had modular ones linked.
[Xoom Android Development] drewski_1:
I like keeping the ROM's browser so do Full Modular.

Stock shouldn't be an issue, fi you're OK with the removal of ROM's launcher, browser, & messaging app.
[Xoom Android Development] sigfridov:
Try this #4800

Folow this:

http://xdaforums.com/showpost.php?p=49498749&postcount=480

THe BigPart instrucction produce some misundertanding with thr OmniROM.

Try and let me know

Regards
[Xoom Android Development] Vnvjeep:
Mail stuck in outbox

I seem to be having an issue with the included Email app when hooking up to my work Exchange account... Email will get stuck in the outbox. The only way to clear it is to reboot, and then it gets sent when it comes back up. When I try to send more mail, then same thing happens, forcing me to reboot to get the mail to clear.

I have totally rebuilt the email accounts from scratch, wiped cache, etc... and I'm not having this issue on my Nexus 7 which I presume is running the same version of com.android.email? On my Xoom, it shows as version 4.4.2-eng.ubuntu.20140116.191149... on my nexus it shows as 6.1-937116...

Any ideas? (and I would rather not use a different email app like Touchdown -- I prefer the stock client)

Thanks,

-Mike
[Xoom Android Development] rmcsc:
I had been following the instructions in the OP, but had failed to get it running a couple times. Found some instructions later in the thread which helped; Xoom is working fine now on KK. Thanks.

That is precisely what I did! It worked wonderfully. Many thanks!
[Xoom Android Development] notbrodie:
I use latest banks core gapps. no fluff

Sent from my Nexus 5
[Xoom Android Development] drag83494:
TWRP Recovery password?!

I flashed (from TWRP Touch recovery) R.A.H._TWRPv2.6.3_BigPart_selinux.zip.

Now I can't even access recovery because it asks me a password.

What password I'm supposed to enter?

Thanks
[Xoom Android Development] kmcrane:
Hit cancel.. It says it somewhere to Ignore that And hit cancel.
[Xoom Android Development] notbrodie:
yep, hit cancel and then format data

Sent from my Nexus 5
[Xoom Android Development] GuiPoM:
Hello!

I give a try to this Rom and I am really pleased to see people are still maintaining this device! First this is of course a great work, I went through all steps including big part very easily and Omnirom is starting as expected.

But I have one major issue: I mainly use my xoom to watch movies from YouTube. Each time I play a movie, the tablet is hanging then hard rebooting. As I was running apreviously a Rom from dreamcli with a custom kernel he sent to me, I suspect I am facing here the same issue. Can you confirm if the GPU part of the kernel has been tweaked (timings ...) or overclocked by default? If so, my xoom does not support that and crashes....

If it can be helpful, I can provides dumps when it crashes.

MANY thanks for your work!
[Xoom Android Development] notbrodie:
it was GPU overclocked, but it was reverted. what's the date on your build?

I've been watching YouTube videos and playing retroarch gba emulator without issue. make sure you are not flashing any kernels after flashing the rom

Sent from my Nexus 5
[Xoom Android Development] GuiPoM:
I did the installation exactly as written in the first post, I did not flash any kernel. Just Rom, gapps and supersu.

Rom version is omni-4.4.2-20140116-1829+0100-wingray-HOMEMADE
[Xoom Android Development] sigfridov:
Follow #480

Try this:

http://xdaforums.com/showpost.php?p=49498749&postcount=480

And please read each line carefully and follow it, if so, you will get the expected results
[Xoom Android Development] John.Spence1:
Just to give everyone an update. I followed the instructions, and it's working great. Thanks for all the help.
[Xoom Android Development] sigfridov:
Great

Happy to ear that!!
[Xoom Android Development] drag83494:
Indeed there was a "cancel" button. So the problem is solved.

But.. when I went to "advanced wipe" I couldn't wipe anything (it gave me error "failed - not possible to mount /cache partition" ) , and I tried several times. So I gave up and went straight to install the rom (Omnirom zip). The installation went fine (and during installation it wrote "BigPart partitioned"). But before installation I had EOS 4 - Android 4.4.2 installed and when the system reboot Omnirom log showed but after 20-30 seconds an error (by Android, not from the recovery) showed "Data can't be decrypted. you have to do a factor reset" but of course when I tried to reboot in recovery to factory reset I coudn't (same error above: wipe failed).

Hence,is there any way to force wipe? maybe from computer?

Thanks
[Xoom Android Development] kmcrane:
Reboot to recovery. Format data... Then reboot recovery. Do a factory reset (or basically just click wipe then swipe) then choose advanced wipe click everything except sd card.. When finished flash rom, then gapps then su.

And boot... It takes a while 5-10 mins.
[Xoom Android Development] GuiPoM:
I did some tests again and my Xoom reboots or hangs as soon as I play a video on Youtube. Right after starting I am able to play video for about 15 seconds then it starts crashing. And finally reboots.

/proc/last_kmsg is here, not sure it provides useful information : http://pastebin.com/ai5CPFFV

As my Xoom is my daily driver and Youtube my most used application, any help would be appreciated :)
[Xoom Android Development] drag83494:
Thank you very much. it worked!
[Xoom Android Development] sigfridov:
That is the way!!!

Congratulations!!

Many guys hurry up the process jumpimg a few instrucctions which brake the process.

Good news!!
[Xoom Android Development] notbrodie:
how far overclocked is your cpu? I'm just a layman, but the crash is being caused by a hard lockup of cpu1. try lowering the max freq

Sent from my Nexus 5
[Xoom Android Development] charos:
Anyone has a link for the changelog of o.t.a. updates?
[Xoom Android Development] halomademeapc:
http://www.duckbox.info/android/omni-4.4.2/CHANGES.txt

Right above the changelog in post 2
[Xoom Android Development] GuiPoM:
This is the problem, it is not overclock at all, stock configuration coming from the Rom. Or, by default, it is, and this was my initial question.

edit: I also tried to update settings in Performance section, by reducing frequency from 1000GHz to 800MHz. Same issue, my Xoom freezes and reboots !
[Xoom Android Development] alivelee6:
Sweep2Wake error

Cannot wake it because a white screen happen

Why
[Xoom Android Development] Alxoom33:
OC is not your issue. I have been running on at 1600 ghz forever.
[Xoom Android Development] notbrodie:
different silicon can take different amounts of overclock. not all chips are created equally. however, in the case of the xoom, i'm pretty sure most of them should be able to handle at least 1.4ghz
[Xoom Android Development] Vnvjeep:
Mine will freeze up after about 1 min if I run at 1600... 1400 is as high as I've been able to keep it stable.
[Xoom Android Development] GuiPoM:
So what could be the issue? My xoom is rock stable on stock Roms so this must be a setting that cause my issue, but which one???
[Xoom Android Development] doubley_m:
Hey guys, just a quick question.

What would be the procedure to switch back to a non Bigpart ROM such as the latest stable Cyanogenmod? I read somewhere that you'd need to flash an alternative recovery? I thought I could leave the partitions as they were but when I tried to flash Cyanogenmod it wouldn't boot so had to put Omni back on there.

Thanks for any help!
[Xoom Android Development] notbrodie:
why not just install the latest bigpart cm? it's the same as non-bp cm.

Sent from my Nexus 5
[Xoom Android Development] Alxoom33:
Some processors just can't handle the oc'g. Its hit or miss.
[Xoom Android Development] drewski_1:
what's the latest stable CM?

there's a CM10.1 BigPart boot.img in the original BIg Part thread. if you're looking to flash 10.1.3 you can flash that after you flash the main CM 10.1 ROM zip

http://xdaforums.com/showthread.php?t=2506997
[Xoom Android Development] noeldc:
Updated and working beautifully. Xoom really is the tablet that just won't quit -- never imagined I would be running KitKat on it.

However, I'm not a fan of the phone mode. Is proper tablet mode on the horizon?

Keep up the good work!
[Xoom Android Development] drewski_1:
Unlikely. Google dropped that with 4.2 following in the footsteps of iOS' one interface for all size devices.

Matias Duarte is an idiot ?

A rich idiot, but an idiot nonetheless.
[Xoom Android Development] notbrodie:
that's great, but it would still be nice to have the left-side buttons. or right-side for the southpaws. i wish Google would just leave it up to the user
[Xoom Android Development] Blondblueyed_girl:
Can I please ask that a change be made on the 1st page of instructions

ie.

3. Reboot into recovery. Flash TWRP BigPart.

4. Reboot into recovery. Go into wipe menu. Select "Advanced Wipe".

I Think this should read:-

3) Reboot into recovery. Flash TWRP BigPart. Don't reboot just yet

4) Go back into wipe menu and wipe everything but /sdcard.

I got into the can't mount cache problem and soft bricked my xoom.

Finally after two days I found out why (I think) I re-flashed the pre Bigpart TWRP loaded Eos3 and everything was ok.

Then I followed the instruction's here http://xdaforums.com/showthread.php?t=2506997 and everything turned out ok.

Its Just a little change in the instruction's but made a big diferance. Its that bit at the end of number 3 (Don't reboot just yet)

Please feel free to disagree.
[Xoom Android Development] sigfridov:
Follow the instructions

If you pay attention in the Schischu instructions, you will see a link "SOURCE", wich move you to BigPart instructions, then it is not selfsuported, you need to Bigpart first, then you can follow Sichischu instructions.

In the Bigpart instructions, in the POIN 9, there is some confusion regarding what you have to flash to.

In this point you need just your OMIN, GAPPS and SU, also some additional feature ZIP file that you want to flash.

I agree with you... with your clarification, I hope it be usefull for more and more people tht love our old XOOM tablet.
[Xoom Android Development] istrait:
First things first... Loving this rom... I am amazed that our old xoom still is getting updates... My thanks to all the very hardworking developers...

I do have an oddity. I am using set CPU for root to have speed profiles. I find that almost every time when I wake the tablet, the speed is showing and acting like it is set to 216 MHz. Set cpu shows the correct speed range but is showing the 216 as the current speed until I touch 1.5 GHz and it resets to the correct speeds I.e. moving within the speed range for the profile.. I have all the profiles set to performance with different speeds based on state of tablet.

Is it the set CPU app or something else? What does everyone think?
[Xoom Android Development] Schischu:
Ok I now also have sleep2deaths. There is some serious wrong in our kernel.

Will check with Prio 1+.
[Xoom Android Development] GuiPoM:
Now 3 days that I am not able to use my Xoom anymore, so I will revert to my old rom. If you have any test you would like me to run before reverting, please let me know. I really would like to keep omnirom but as I constantly get hard reset each time I start a video or a game, it prevents me from using it. As I did not change anything from the initial setup (only added my google account) there must be an issue somewhere ... but I can't find where !
[Xoom Android Development] shpitz461:
Mine has been rock-solid with latest Stingray OTA. If I OC to 1.6 the tab will reboot randomly, but it is very solid and happy @ 1.5GHz. Youtube videos, Nova launcher, a few card/mahjong games work great, no complaints.

I think people with issues should provide logs to Schischu, otherwise I'm not sure he'd be able to solve any thing...
[Xoom Android Development] pots22:
Perfect release 16/01/2014

Omni 16/01/2014

Pa_Gapp-mini 17/01/2014

Animation 0.25

Cpu 1.4

Engine ART

Launcher APEX free.

Incredible speed, very stable, play with Real racing 3 long hours without bug.

Only video codec and when i install flashplayer my and prefered TV application can't open the plugin.

Impatient to see new ROM without bigpart to make more test. :)
[Xoom Android Development] dsbnz:
Have you noticed any difference between dalvik/art ?
[Xoom Android Development] GuiPoM:
I already posted my kernel logs. The problem is I am pretty sure this work is working on most of the devices. My has not a good piece of hardware and is really sensitive to the tweaks done in the kernel (timings, voltage, clocking, ...) It really works well on stock roms (and by extension stock kernels), but as soon as I switch to custom roms, I have this issue.

Can I run a stock kernel with omnirom ?
[Xoom Android Development] shpitz461:
I don't think there's stock 4.4 bigpart kernel available, there's an AOSP 4.3 bigpart kernel in the origianl bigpart thread, but i don't think it'll work...

Thanks for providing logs, I'm sure that will be helpful to Schischu...
[Xoom Android Development] pots22:
ART

Yes i note a difference for the time to open all applications working with ART and a global amélioration of the fluidity

The problem at each new update for the first boot long time for the optimisation of each applications installed on the Tab.

With Dalvik engine each time you open an application the system decompile the app and lunch the app.

With ART during the first installation of the app the system decompile the app and it's finish next time you open this app don't need to decompile

Only app take more place and some old app not compatible
[Xoom Android Development] P00r:
For me increasing lowest CPU speed to 456 fixed the sleep issue permanently
[Xoom Android Development] notbrodie:
that's odd. it would be understandable if you were undervolting, but xoom doesn't support that. i've only had one SOD since 4.4 came out, and only one or two in 6+ months running eos4.
[Xoom Android Development] drewski_1:
I've seen this on my N7. Too low min causing SODs.

I'm ignorant. What is the stock min?
[Xoom Android Development] notbrodie:
no. stock minimum is 216mhz. i've never had an issue with that freq, ever. in fact, it's the freq the xoom spends the most time at. usually 6-8hrs per charge cycle
[Xoom Android Development] Rularn:
Clear All Button

Is there a way to make the clear all button in the recents view larger? Same for the memory indicator...

Otherwise, love the ROM.
[Xoom Android Development] notbrodie:
it's a bit OT, but your system is better off with you ignoring those two things. clearing recents does nothing for your battery and unused ram is wasted ram. android will reclaim memory as necessary.

in fact, clearing recents is likely to negatively impact battery life. for all the same reasons that task killers are very negatively criticized

Sent from my Nexus 5
[Xoom Android Development] Obsy:
There is an option for Clear all button.... check Interface > More ;)
[Xoom Android Development] ahmed007:
play music is force closing for me on the new update anyone else have such problem
[Xoom Android Development] notbrodie:
No problem here. are you using a gapps package that includes play music?

Sent from my Xoom
[Xoom Android Development] ahmed007:
Yes using full modular pa gapps I this its from 30th Dec 2013 need to update?
[Xoom Android Development] notbrodie:
I would say yes. new play services came out. or try removing play music and reinstalling from play store

Sent from my Xoom
[Xoom Android Development] ahmed007:
will just flash the new gapps and see what happens :good:

---------- Post added at 10:47 PM ---------- Previous post was at 10:15 PM ----------

Flashed new gapps all working well now
[Xoom Android Development] grey.ghost:
This coupled with a few select xposed mods have really brought the old xoom to life. No issues to speak of yet. Nice work devs!
[Xoom Android Development] P00r:
My sod hapened with this rom, I increased the min speed and haven't had issue since. Never had this on eos but had seen this with other tablet/rom and the fix was alway to increase the min speed. Work for me...
[Xoom Android Development] Schischu:
It seems to me that sleep2death only happens if using CPU ondmand.

Can everybody who has this problem check if that is the case, and if so switch to interactive?

I have done so and have not gotten any sleep2death with interactive anymore in the last 3 days.
[Xoom Android Development] Rularn:
I know where the checkbox is for the button. That wasn't my question. I was asking if it was possible to make it view larger. I'm guessing the answer is 'no'.

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

I had the same problem on a clean install of omni too for the stock music app. It went away after some reboots and playing around with it. Probably had something to do with updates from playstore as well.

I used Banks GAPPS core.
[Xoom Android Development] P00r:
My sleep issue where with the default, it is in interactive right now! but not sure at what value it was at the time. I will lower the CPU speed back to default since the issue was with an early release, just for the sake of testing
[Xoom Android Development] P00r:
Came back tonite and had to reset, so interactive doesn't fix it for me, min speed does tho. Still a great rom AFAI Concerned
[Xoom Android Development] kmcrane:
Sio and Interactive. Min at stock, max at 1200 no issues since day 1.
[Xoom Android Development] notbrodie:
ROW, Ondemand, ART, 216mhz/1600mhz. buttery!
[Xoom Android Development] dsbnz:
Ive found row/on demand pretty good also, with animations set to 1.5
[Xoom Android Development] Prack:
Love the rom, only question is why is the superSU icon not in the launcher? Seems the only place I can get to it is in settings - supersu.

I tried the apk from the store and flashing the v.1.91 zip, tried multiple launchers, seems superSU icon is always hidden from the launcher. Not really a big deal but this is my only android device doing this.
[Xoom Android Development] notbrodie:
I think it has to do with omni integrating supersu into the system. you probably not bother flashing supersu from now on... ymmv

Sent from my Nexus 5