Originally Posted by luke.arran

Thanks my Xoom 2 is running great again!

Also add this warning. Do NOT remove the Launcher2 app if you do then your Xoom 2 will never boot again and the is no current way to fix this because of the locked bootloader.

That's my question, why do you even need to freeze the stock launcher if you've set adwlauncher as the default.. like what's the point of that step of freezing the stock launcher, it shouldn't impact performance.


Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

Originally Posted by big ach

That's my question, why do you even need to freeze the stock launcher if you've set adwlauncher as the default.. like what's the point of that step of freezing the stock launcher, it shouldn't impact performance.


Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

No he is right, because the stock launcher takes a big bite out of your RAM around 100MB. And even if you do have another launcher running that stock launcher always seems to be in the background on my tablet.

Originally Posted by luke.arran

No he is right, because the stock launcher takes a big bite out of your RAM around 100MB. And even if you do have another launcher running that stock launcher always seems to be in the background on my tablet.

Yeah but won't freezing the launcher (or changing its name to launcher2.apk.bak) cause problems if your tablet faces a failure and the adwlauncher crashes?


EDIT: I guess titanium backup unfreezes apps if you do a wipe so the best option is to freeze the stock launcher (NOT uninstall it and NOT rename it)

Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

Over 1 week now and not 1 reboot.

I can't answer these questions on the launcher?

All I know is this works for me, I have had not 1 freeze or reboot, so the stock launcher can stay frozen.
(it may have absolutely nothing to do with it, but I really don't care)

Hi after several days over GO Laucher EX (or HD "Tablet version but less customizable") with Setcpu 1200 1200 performance and etc....

only 1 reboot when several web pages were opened on stock browser with flash videos etc.
I've noticed that now when apps stops to work it goes back to home instead of reboot except that time.
Almost no free ram and that's seems to be the clue..Stock launcher doesn´t free enought memory

And battery drains suddenly stopped.

Super happy man . More fluid launcher, more customizable, and also wifi starts to work better when comes back from sleeping

Thanks for not to give up!

Have to say... this solution seems to be working very well. I'm running set CPU in conjunction with auto memory manager set to "aggressive" and AdwLauncher Ex!

Using many apps that in the past would give me reboots, but now they are working flawlessly.

Thank you very much for this awesome contribution!


Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE

I'm Xoom 1 user and also having annoying reboots you described here. Most of all it happens when watching movies or iptv in player.
But isn't setting cpu frequency to 1200min will force cpu run at 1200 not less all the time? It probably may overheat the cpu and sounds dangerous.

Originally Posted by Neolo

I'm Xoom 1 user and also having annoying reboots you described here. Most of all it happens when watching movies or iptv in player.
But isn't setting cpu frequency to 1200min will force cpu run at 1200 not less all the time? It probably may overheat the cpu and sounds dangerous.

When its in use yes, but you also set a second profile to turn down the cpu to a lower value when the screen turns off so you don't drain battery and cause overheating!


So far - I'm running this method without any problems, no noticeable battery drain or extra heat in anyway!

Originally Posted by big ach

When its in use yes, but you also set a second profile to turn down the cpu to a lower value when the screen turns off so you don't drain battery and cause overheating!


So far - I'm running this method without any problems, no noticeable battery drain or extra heat in anyway!

I'm currently running on stock kernel without ability to scale over 1000. Tried to set to performance governor only, but failed and got regular reboot during usage. Will try your method.
Seems to be it's operating system problem. Don't understand why motorola still didn't resolved it, including that fact that problem also present in first Xoom model.

Worked a bit around with your solutions and stabled on the following:

• Stock launcher frozen;
• SetCPU profiles:
  1. Screen ON/unlocked: Governor OnDemand (1200-800) with Noop Scheduler
  2. Screen OFF: Governor standard hotplug (800-300) with noop scheduler

It looks like moto_hotplug governor doesn't work quite well but I also noticed some glitches on systemui.apk. Whenever you turn your screen on and unlock doesn't show smooth you must turn off screen and try again... if you unlock with a laggy unlocker the whole system will be a mess.

With those setting I'm not having reboots, just some lags here and there; battey, however, lasts much less due to ondemand governor.