CM7 B2TF w/Faux Kernel & Launcher Pro issues - Atrix 4G General

Anyone running this combination?
CM7 B2TF, Faux kernel (any version, overclocked or not) and Launcher pro?
I seem to get a ton of force closes of launcher pro all throughout the day, and a 3 or 4 times a week I'll look at my phone and notice it has randomly shut off.
I'm not undervolting and the phone does not run hot.
Thoughts?

i've had that before but i think it was due to a kernel or radio. I have cm7 with faux
1.30 and haven't had any problems. Maybe a random reboot everyweek but i can live with it.

waktasz said:
Anyone running this combination?
CM7 B2TF, Faux kernel (any version, overclocked or not) and Launcher pro?
I seem to get a ton of force closes of launcher pro all throughout the day, and a 3 or 4 times a week I'll look at my phone and notice it has randomly shut off.
I'm not undervolting and the phone does not run hot.
Thoughts?
Click to expand...
Click to collapse
I had the same configuration as you and after installation i had a lot of FCs. I rebooted the phone and fixed the permissions and problem was solved.

I'm using ADW EX (which I don't like as much as Launcher Pro) but no FCs in the last day and a half.

I was running this combo for a while, LP never force closed but if you are running launcher pro with the LP Widgets such as the twitter or friends you may have a couple.
I used to have the Facebook/twitter widget on one home screen and it would force close all the time, once I removed the widget I never get a force close, this problem goes back to moto builds for me.
Sent from my Motorola Atrix 4G MB860 using Tapatalk

Thanks. I was actually thinking that might have something to do with it because the facebook widget would seem to hang from time to time. I did end up getting rid of that but I still use the calendar widget because I use it all the time.

Yup that's why I left LP+ for ADW EX. LP+ just went crazy on me and started force closing constantly, I tried changing every setting I could but nothing made a difference. ADW hardly ever force closes. Like you I had preferred LP to ADW, but not anymore! ADW pros far outweighs LP pros imo.
Sent from my MB860 using xda premium

waktasz said:
Anyone running this combination?
CM7 B2TF, Faux kernel (any version, overclocked or not) and Launcher pro?
I seem to get a ton of force closes of launcher pro all throughout the day, and a 3 or 4 times a week I'll look at my phone and notice it has randomly shut off.
I'm not undervolting and the phone does not run hot.
Thoughts?
Click to expand...
Click to collapse
Same here. Switched to Go Launcher and no problems now. Also fixed permissions.

Preaching to the choir my dude.
FC's everywhere, random reboots, GPS blows.
Sadly, I think it's the best we have so I'm just dealing with it now.

my best advice? don't run cm7 b2tf....
run weekly 4.

Related

Eris rebooting spontaneously

I am running Aloysius v12. I have removed most of the rosie stuff. I am using JIT. Installed ADW but running Launcher Pro.
My phone reboots itself about 4 times a day. It doesnt matter if it is charging, or if I am running an app of some kind, or on the phone. It will just reboot. First it started while running ADW and oc'd to 786. So, I switched to LP and slowed it down to 748. Still reboots.
What can be causing this?
The most likely culprit is overclocking.
Keep moving your maximum down.
BigBeefy said:
I am running Aloysius v12. I have removed most of the rosie stuff. I am using JIT. Installed ADW but running Launcher Pro.
My phone reboots itself about 4 times a day. It doesnt matter if it is charging, or if I am running an app of some kind, or on the phone. It will just reboot. First it started while running ADW and oc'd to 786. So, I switched to LP and slowed it down to 748. Still reboots.
What can be causing this?
Click to expand...
Click to collapse
slow down oc to 710, but the reboots are going to keep happening until you remove JIT. It is very unstable and WILL cause spontaneous reboots.
OK, thanks,
I read over in another forum another reason for random rebooting.
"Only MOD from there that gave me issues was the battery removal from task bar. It would make the phone random reboot. Others had the same issue."
I am using Droidkevlar's MOD:
v.03 Removed time from task bar (thanks to jschisurf for this)
Multiupload.com - upload your files to multiple file hosting sites!
I wonder if this is why my phone is rebooting? I didnt do the battery removal mod, but the time removal. Battery icon changed to the round battery indicator. Any thoughts on this? Or is it more likely it is due to the JIT? I have removed JIT and slowed down to 710
I have disabled JIT.
Phone just rebooted itself again. Indication LED was flashing green while rebooting. I got a text message right before it rebooted. Didnt start at the green skaters, just went straight to the nexus boot animations.
This is getting really annoying now.
I would suggest a reflash of your rom. Seems like maybe one of your apps or customizations is messing around with the phone.
If you don't get the green skaters boot screen on your crash reboot, it's not totally rebooting. It sounds like your Home may be crashing. Does this happen when running other homes?
nimdae said:
If you don't get the green skaters boot screen on your crash reboot, it's not totally rebooting. It sounds like your Home may be crashing. Does this happen when running other homes?
Click to expand...
Click to collapse
It started happening with ADW home. So, I switched to Launcher Pro. It has only done it once with LP.
I havent added any new apps before this all started.
I have added a MOD to my notification bar. That is the only thing different. I have been using Aloysius v12 since it was posted. I do have Rosie deleted tho. I deleted Rosie when I added my JIT. Now that I have disabled JIT, I wonder if reflashing v12 will help out.
Can I reflash v12 without doing a full wipe and retain all my apps and settings?
I have Eris lighting 2.5 and I have the same thing happing with ADW as the home scree. n
Clear dalvik again.
Nanajoth said:
Clear dalvik again.
Click to expand...
Click to collapse
Do I do a nand first?
It would not hurt.
didnt work. But thanks.
I had the same problem and worked for me, what applications do you have?
Actually, I just posted another thread about my desk clock app posting celsius temp instead of fahrenheit and thought you were responding to that one. I did however do a nand back up and delvick wipe. I will watch to see if I reboot at all tomorrow. Sorry, I got confused on which thread I was reading.
-------------------------------------
Sent via the XDA Tapatalk App
Does your phone run hot? This was happening to my phone constantly (like I couldn't even get past skateboards sometimes) so I did a rollback to stock 1.5 then ota and vzw replaced it in store only to get home and have it happen again. I had them replace the battery after and it hasn't happened since.
sickbox said:
Does your phone run hot? This was happening to my phone constantly (like I couldn't even get past skateboards sometimes) so I did a rollback to stock 1.5 then ota and vzw replaced it in store only to get home and have it happen again. I had them replace the battery after and it hasn't happened since.
Click to expand...
Click to collapse
My phone never runs hot. I am only clocked to 710. No JIT.
Make sure you are using the Passive SetCPU widget, not the Active.
Try disabling A2SD.
I too had this same problem and after having the battery replaced and flashing a fresh rom all is fine.

100% Wake lock?

Spare parts is reporting that my awake time is 100% and the partial wake usage reports android system is the cause. I can only assume the community has found and fixed this issue, but I didn't see any topics about it in this forum. Thanks.
I posted about this a couple times in a few places. It started with the DI07 update, and seems to have been fixed with the DI18 update.
I noticed the same thing, even with di18. I was running ADW as my launcher. I switched back to TW, did the airplane toggle, and my run avg has dropped back to single digits.
I might try a different launcher later to see if it is a problem with all launchers, or just ADW.
Correction... I was using launcher pro, not adw. Might try adw next.
You might want to check sensor usage in spare parts also. I've seen the Camera app use the sensors even after closing out of it.

phone randomly reboot / force close

I picked my Nexus S up this am as the store opened at 9am. I powered it on and away it went it had all of my apps dl in minutes.I had to go into work so I just let it charge on my car charger. Got to work and went to start Cardio trainer ( which is an app I use daily for about 3-5 hours per day) it immediately force closed. Force closes each time I try and use it. So i sent message to dev. The next thing I know I get a message saying that Beautiful Widgets geolocation is getting false reading from the GPS and it force closes. The GPS has been spotty. When first initiated it took over 10 minutes to get a lock. Turned it off and tried again and it took 7 minutes. The third time it was about 15 seconds and since then it alternates back and forth from almost instant to minutes again. What concerns me is that the accuracy just bounces back and forth from 32.6 ft to 16.3 ft and anywhere in between and really never stabilizes. This may be normal for this type GPS systems(I don't know) Also I have the old market and cannot find a link for the new market.Wasn't Gingerbread suppose to come with the new market? So far I am impressed with the smoothness of the system but not with the GPS. Also the lInpack scores are lower than on the Vibrant. Appears to be very solid. Anyone else have any of these problems?
tenbeau said:
I picked my Nexus S up this am as the store opened at 9am. I powered it on and away it went it had all of my apps dl in minutes.I had to go into work so I just let it charge on my car charger. Got to work and went to start Cardio trainer ( which is an app I use daily for about 3-5 hours per day) it immediately force closed. Force closes each time I try and use it. So i sent message to dev. The next thing I know I get a message saying that Beautiful Widgets geolocation is getting false reading from the GPS and it force closes. The GPS has been spotty. When first initiated it took over 10 minutes to get a lock. Turned it off and tried again and it took 7 minutes. The third time it was about 15 seconds and since then it alternates back and forth from almost instant to minutes again. What concerns me is that the accuracy just bounces back and forth from 32.6 ft to 16.3 ft and anywhere in between and really never stabilizes. This may be normal for this type GPS systems(I don't know) Also I have the old market and cannot find a link for the new market.Wasn't Gingerbread suppose to come with the new market? So far I am impressed with the smoothness of the system but not with the GPS. Also the lInpack scores are lower than on the Vibrant. Appears to be very solid. Anyone else have any of these problems?
Click to expand...
Click to collapse
It sounds like a GPS problem with your device, Just get it swapped mate
JD
I've only had FCs using the new google maps so far.
Random FC for me in maps, market and gallery :-/
ive yet to experience a FC
Cardio trainer is not working for me either, I am wondering if the dev's need to update it for 2.3, I also can't get vlingo to work.
JupiterDroid said:
It sounds like a GPS problem with your device, Just get it swapped mate
JD
Click to expand...
Click to collapse
I don't think it's a gps thing, I can't even get into cardio without it FC, my GPS locks without a problem.
phone randomly goes to boot animation screen
Ok, so it appears something is wrong with my phone. Every once in a while, i'll look down on my phone or in the middle of doing something, and it will go to the boot animation screen. Most of the time, the boot animation screen is dimmer than on normal start up. It will eventually go back to the ui, which I will then have to restart my phone because it won't connect to wifi or 3g.
Anyone else had this problem? Think it's worthy of getting a replacement from bestbuy or a glitch that should be fixed with an ota?
I haven't seen anything like this yet, though I suppose I don't keep my eye on my phone constantly, so I suppose it could have happened while I wasn't looking. No WiFi or 3G problems, either.
Sounds like you've got a serious issue there if you're seeing it a lot, though. I would get it replaced. Unless you're running a third-party ROM or some other non-stock mod, in which case dump it first and see if the problem is being caused by that.
Yea I had this happen twice. At gym was changing a track with Bluetooth headphones and went to dimmer bootscreen had to pull battery. And another time I had to reapply all my Widgets on my homescreen. I'm on CM7 rom
Sent from my Nexus S using XDA App
Are you using a custom ROM/kernel/SetCPU? Those problems sound like the ones the D1 has when it's clocked past a stable speed.
Sent from my Nexus S using XDA App
rocketragz said:
Ok, so it appears something is wrong with my phone. Every once in a while, i'll look down on my phone or in the middle of doing something, and it will go to the boot animation screen. Most of the time, the boot animation screen is dimmer than on normal start up. It will eventually go back to the ui, which I will then have to restart my phone because it won't connect to wifi or 3g.
Anyone else had this problem? Think it's worthy of getting a replacement from bestbuy or a glitch that should be fixed with an ota?
Click to expand...
Click to collapse
I'd look at the software you've added since the phone was purchased as the first primary suspect. Weird widgets, background services, live wallpapers, background syncing app, something like that...
You'd want to wipe/reset the phone before a return anyways, so why not do a factory wipe/reset from the settings/privacy menu, then start off with a fresh phone (software wise)? Be conservative in what apps you install at first, and check for stability; then slowly add back the stuff you'd have one by one and see which app from the Market causes the glitch.
I think that's a bit more fair to Samsung, Best Buy, and whoever ends up with the device as a refurb, than returning what is probably not bad hardware to the store.
demo23019 said:
Yea I had this happen twice. At gym was changing a track with Bluetooth headphones and went to dimmer bootscreen had to pull battery. And another time I had to reapply all my Widgets on my homescreen. I'm on CM7 rom
Click to expand...
Click to collapse
Hmmm...and you don't think the fact that you're using ALPHA level firmware that is known to have some bugs in it, might be your problem?
I'd expect that kind of thing with CM as long as it's alpha, and even beta. I wouldn't be surprised with it even on the RC versions. It's experimental until Team Douche releases an actual ready-for-prime-time version.
Are you using a custom ROM/kernel/SetCPU?
Click to expand...
Click to collapse
Nope, I'm not even rooted. I am however running ADW ex launcher. As far as widgets, the only widget i have running is the weather/news that came stock on the phone. As far as apps, I really don't have anything crazy downloaded or running.
rocketragz said:
Nope, I'm not even rooted. I am however running ADW ex launcher. As far as widgets, the only widget i have running is the weather/news that came stock on the phone. As far as apps, I really don't have anything crazy downloaded or running.
Click to expand...
Click to collapse
I've been running ADW.Launcher without problems up to now. I just upgraded to ADWLauncher EX last night; I'll post here again if I start seeing this issue.
this is similar to the other topic.
Random Reboots, we call it on the SGS (samsung galaxy s) side
hoping for the best, it is not the same deadly problem we found on some of the 16GB SGS phones, that eventually lead to the corruption / destruction of the internal SD
but those were the signs.
so i'm really hoping that is not the same problem, else i'll really be pissed with Samsung to produce yet another crappy phone with cheap internal parts.
it should not be, as i saw pictures of the innards of the SNS (samsung nexus s) and it was clearly showing SandDisk for the 16GB internal SD
Random Reboots
A couple of times I've had the Nexus S reboot, once when I was in the middle of a call and once again as I was messing around with the settings.
I'm running 2.3.1, th latest build GRH78, does anyone have an idea as to why the random reboots are occurring?
Thanks in advance for your help
Sent from my Nexus S using XDA App
Let's please keep it friendly and on topic here. Thank you
reception bar is stable but on active call it gets disconnected and i have to turn the phone off and on right away thia happens pretty often. I called samsung and they have no solution but to tell to go get it exchanged. This is already a second device.
Sent from my Nexus S using XDA App
Same thing happens to me.. now 4 times its happened to me
Sent from my Nexus S using XDA App

Why does my DZ fail me when I need it the most

Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer
makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?
As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.
its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said
Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html

(xoom 2) XOOM 2 10.1 Freezing & Reboots – A SOLUTION!

I just wanted to share with you my recent issue & solution to the XOOM 2 rebooting issue.
Now to give you an overview of my situation, I purchased the XOOM 2 10.1 UK back in January 2012.
I use it almost every single day. No surprises I was getting random screen freezing followed by reboots every single day. Most days twice!
Now I was hoping that when the update happen back around 2 months ago that it would solve this issue. It never.
In fact my freezing & reboots were happening more frequent.
Basically within 5-10 mins of using the Xoom2 it would reboot.
Some days I just wished I could throw the dam thing through the wall.
I rooted using Dan’s method. The only method. & tried various ways to solve the issue.
NOTHING worked.
In fact, I was convinced that my rooting & installing things that should not be there was making the reboots worse.
So I cleaned up my Xoom 2, went into recovery, wiped cache & cleaned data & rebooted.
This still did not work.
Then I tried task managers, cache cleaners & even paid for that system panel app that logs all apps & usage.
Nothing worked; I was still getting the reboots. Everyday.
So after looking over many Xoom 2 forums & with many issues and complaints about this issue, I was close to selling & getting an iPad.
I was convinced it was hardware.
Then I tried this way:
1. I rooted.
2. I installed ADW Launcher & made default.
3. I installed SetCPU
4. I installed Titanium Backup
5. I froze the stock ‘launcher’ – (whatever you do – do not un-install any app, you CANNOT update Xoom if you do)
6. I changed CPU from ‘hotplugmoto’ to ‘performance’ 1200min 1200max
(I know you might think this uses lots of battery but I found not)
7. Set up setCPU profile for ‘screen off’ I use ‘on demand / 300 to 600’
Battery over night on this setting did not go down by 1%
8. Rebooted.
After 4 days of constant use & trying so hard to get the Xoom to freeze & reboot – I can’t.
This method works.
I have surfed using ‘Firefox’ while using ‘Currents’ while using ‘Google+’ while downloading files and steaming music via ‘Google Music’. I have open every single app & been quickly switching between them all trying to over load the system.
Nothing will freeze or reboot my XOOM 2.
What I can get from this is that the Xoom 2 works perfectly.
With the high CPU set, it is so fluid and lag free. It works almost perfectly now. It also means the hardware is absolutely fine.
Maybe with newer firmware updates in the future this will be sorted naturally.
I makes me think something with the high CPU means a bug in the processing won’t make the Xoom freeze & reboot.
Until then this method works for me and I can’t see why it won’t work for you.
If you are having this issue I hope this helps.
I messaged you on the Motorola Forums, but I think they may take it down since they don't like talks about rooting.
But thanks for posting this, I will give it a shot.
When you changed to performance 1200 min/1200 max - I'm guessing you also checked set on boot? right?
Yes i ticked set on boot. Make sure you have a screen off profile otherwise it will be running at max all the time.
Hope it works for you.
Sent from my XOOM 2 using Tapatalk 2
Hi,
I froze some bloat before and uninstalled flash 10.3 cause flash streaming online videos didn't work 4 me (neither 10,3 or 11,x), then installed flash 10.2 and all starts to work ok but still 2 or 3 reboots for week.
Also seems that "memory booster" app helps when some apps starts to freeze and u can finish em and free some mem.
So now i'm trying setcpu and then i will do launcher trick
Thx a lot!
Vanpeebles, Did you switch launchers because you think it will help the reboots? or because of personal preference?
List of frozen apps
List of frozen apps 2 months ago without issues:
App used: Ultimate Backup
Amazon Kindle (I dont use it)
Citrix Receiver
Drippler Motorola DROID Xyboard 8.2
Drive
Fuze Meeting
Google+
GoToMeeting
Servicios de estadisticas de dispositivo ("Device statistics Services")
Twonky
Good luck everybody!
Now i'm not expecting ICS, this is working almost perfect. Let's see setcpu improve.
It does seem that the source of the freezing/reboots is the Motorola Launcher. Since I switched to Go Launcher HD I've definitely seen less freezes.
Hi
I switched launcher on personal preference but to be fair I have had no freezes now for 5 days
So I'm not messing now if it ain't broke.
The reason is I did this is I read 1 post on another forum that someone changed launcher &, this helped him.
So wether launcher or high cpu I'm not bothered
To finally have a working tablet is such a huge relief!
Sent from my GT-I9100 using Tapatalk 2
Thank Vanpeebles,
I did everything you said and now hoping for the best!
Either way, I'm loving ADWLauncher Ex..... sooo fast and snappy!
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
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.
luke.arran said:
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.
Click to expand...
Click to collapse
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
big ach said:
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
Click to expand...
Click to collapse
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.
luke.arran said:
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.
Click to expand...
Click to collapse
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.
Neolo said:
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.
Click to expand...
Click to collapse
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!
big ach said:
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!
Click to expand...
Click to collapse
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:
Screen ON/unlocked: Governor OnDemand (1200-800) with Noop Scheduler
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.

Categories

Resources