Related
Hey evweryone,
Found a VERY strange issue, that seems to be affecting Captivate users as well. This is my second phone that has had this issue, so its not isolated.
The phone works fine when using it, but when it goes to sleep, occasionally (more and more frequently it seems) it will actually turns off. Meaning, when I pull the phone out of my pocket, its off. Has occurred 3 times today, and I'm SURE i didn't accidentally hold the power key.
First, I thought it was the OC kernel, so I reverted to JAC's non-OC kernel, still turns off. Reverted to stock kernel, still happens. I have a slight hunch maybe SetCPU may be causing it to sleep incorrectly, so I un-installed that.
Anyone else run into this issue? Its a PITA when your phone randomly turns off, cant rely on it at all. Thanks!
EDIT: Phone was ON while sitting on my desk while I was writing this, tried to wake it up....it was off
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Puushiki said:
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Click to expand...
Click to collapse
I will try that and see. Anyone else have this issue on any Galaxy S based device (Captivate, Vibrant or Generic Galaxy-S)?
Oh btw, I have the Samsung Vibrant
Puushiki said:
Oh btw, I have the Samsung Vibrant
Click to expand...
Click to collapse
Okay, confirmed by one user. There is a large number of captivate users having this same issue, and a discussion about it in a SetCPU forum (Link ).
No problems here, stock ROM + RyanZA using SetCPU since day one.
Two profiles: conversative
Battery <100%: 400 min; 1000 max
screen off: 400min; 400 max
Are you guys using SetCPU for OC'ing, or for scheduling?
I was having the same issue, wasn't sure what it was and was going to return my Vibrant, and with that in mind had wiped the phone and gone back to stock. Due to a delay in getting to the store, I did re-install things (hey, I do need my phone) and found that the issue had stopped. I did have SetCPU on originally and have not re-installed it, but it's difficult to recall if I had SetCPU on before or after the issue started. I suspected it could have been SetCPU and since I didn't really feel the need to use it, I just didn't bother to install and and wanted to see what would happen.
It did happen again yesterday, but the phone seemed to just lock up on me while I was using it (was as I was using Navigate, got to my destination, locked up, then shut off, more or less), so it might have just been another fluke due to overheating or something.
Anyway, the problem that I had was that I couldn't get the phone to come back on without having to remove and replace the battery. But fortunately, other than yesterday, the issue has not happened since the past Friday (where it happened 4 times that morning vs once per day the 3-4 days prior). The inability to turn it back on might just be an issue with my phone (and it only happens after this force shut down).
ytj87 said:
Are you guys using SetCPU for OC'ing, or for scheduling?
Click to expand...
Click to collapse
Mainly for stress testing, as the OC kernel doesnt need to be configured to OC, its already running at 100/1200. Mainly for scheduling and stress testing. Occasionally for detailed info about CPU (temp, current speed, etc). Hopefully this issue\bug can get worked out, cause SetCPU is a GREAT app.
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
hockeyrcks9901 said:
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
Click to expand...
Click to collapse
Had NO issues today, seems SetCPU was the culprit. Thanks!
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Puushiki said:
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Click to expand...
Click to collapse
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
I have had the same problem and am using SetCPU. I love it, but this shutting down in sleep mode thing is driving me crazy. Gonna try to turn off notifications and move to conservative and will report what happens.
I use SetCPU regularly on my Captivate and only see issues if I change the governor or polling interval, or if I use profiles.
Sent from my SAMSUNG-SGH-I897 using XDA App
hockeyrcks9901 said:
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
Click to expand...
Click to collapse
**** speed aye?
Don't use setcpu!!!!
Sent from my SGH-T959 using XDA App
xaisomboun said:
**** speed aye?
Click to expand...
Click to collapse
lol. That's swype for ya...
Typos and other gibberish courtesy of Swype
I have this problem several times a week. The phone is NOT rooted. What are my options for curing this problem besides rooting?
Thanks for the help.
Samsung Vibrant, Android 2.1, T-Mobile
I read somewhere that Galaxy S users should NOT use conservative and use on demand instead for this reason... not sure though.
this may be posted in the wrong section but i would like everyone running froyo to test this out
HERE IS THE LINK TO GET THE LATEST SETCPU
http://forum.xda-developers.com/showthread.php?t=505419
So I have been doing some experiments on ways to save battery life....I think i have made a break through it is not fully tested i would like for some of you to try it out.
with the latest updates to your ROM itself, setcpu, superuser, and the addition of cache cleaner and the incredible AUTOKILLER (a must have) i have been able to run extremely low setcpu sleep profiles without any noticeable loss of performance.
Believe it or not i have my sleep profile down clocked to 19200mhz with out "noticeable" performance loss
i would like for some of you if possible to try these profile out for a while and see how it works out for you
DEFAULT 480min---whatever you want max (mine is 787) ondemand (for performance)
OR DEFAULT 245min---whatever max (for even more battery savings)
SLEEP 192min---480max ondemand (works great even without sleep to wake lag)
it works dont believe me then check out set cpus new feature "time in state"
open setcpu
go over to info
scroll down a little and you will see the times in state your phones cpu runs in the most
you should now see values at the lowest state of 19200
if this works in theory we can benefit from longer battery life
and faster charging
please try these out and report back to the post or PM me...this could be good
Thanks
UPDATE 8/22 EDIT: some users are having success running an even lower default 19min--whatever max (thats even more savings) will be looking into it
try these even lower profiles
DEFAULT 122min--whatever max (screen ON cpu does not drop below 122mhz)
Screen OFF 19min--245max (no lag just ran pandora and cardio trainer at the same time here no lag from sleep to wake either)
or Screen Off 19min--480 max for more performance
REMEMBER not to have conflicting profiles and to have SCREEN OFF at your highest priority
please post here your own findings and results
Thanks again
UPDATE 08/24/2010
after experimenting with other speeds i have finally settled on these speeds for my personal taste on performance and battery savings
MY FINAL SETTINGS...
DEFAULT 19MIN---786 or whatever MAX on demand
SCREEN OFF 19MIN---480 MAX on demand (highest priority) think deeply about why this is the highest
TEMP <40 19MIN---528MAX (screen off overrides this which cools anyway)
BATT <40 19MIN---604MAX
next more into advanced settings....coming soon
UPDATE 08/26/2010
im almost at the holy grail here
try this set up
SCREEN OFF 19--480 (95 priority)
TEMP <40 19--580 (90 priority)
ADVANCED SETTINGS
SAMPLING RATE---100000
UP THRESHOLD---98
ignore nice ---0
power save bias---0
hit apply (if you like it check set at boot)
ALL CPUS ARE NOT CREATED EQUALLY WE ALL KNOW THIS SO DONT EXPECT MY EXACT SETTING TO WORK FOR EVERY SINGLE PHONE
I CAN ONLY OFFER A STARTING POINT BUT ITS UP TO YOU TO TWEAK IT BUT ITS WORK
I HOPE THIS HELPS
things to notice....
in the main screen in setcpu watch the main frequency values bounce up and down...after a few seconds the values seem to stabilize at the lowest frequency of 19
in time of state screen even when screen on most of the time the 19 freq get the most values
i need a few guys to run, test and monitor the values that i just posted ^^^HERE^^^
this may further the battery life once we stabilize the frequency to 19 most of the time while keep the SAME performance which i think i may have did
run some linpacks and quadrants with those setting
i got
5.4 linpack running 787max
431 quad running 787max
then it drops back to 19 and stabilizes
hope this works and please post all your feed back and setting so we can learn this and get it perfect
thanks
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
thisisreallygay said:
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
Click to expand...
Click to collapse
19 is even lower try it
Oh 19200? Wow I wasn't paying attention well enough. I'll try it.
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
I wonder what it's like when receiving a call. I just set it and I'm not having any lag with just turning it on or anything. I'll test it out with other things. I hope this greatly improves my battery.
roirraW "edor" ehT said:
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
Click to expand...
Click to collapse
shame on you for keeping that secret all to yourself
SHAME
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Search for it on his website, idk what his website is you'll have to search for it. Or download a ROM with it already in it.
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
thisisreallygay said:
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Click to expand...
Click to collapse
hmm last time i was on sense rom sense fell apart if you clocked lower than 245
epically receiving a phone call
but i only test this method on froyo
I've heard that too. Although I don't know what is bad about it.
sh_mohanna said:
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
HERE
http://forum.xda-developers.com/showthread.php?t=505419
eklipze said:
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
Click to expand...
Click to collapse
i heard that too but all froyo dev have a 245 to 710 stock on their roms
thats why i kinda spilt the two profiles and why 245min--- is experimental
leave your screen off for a while and see if the ime of state shows up
also make sure not to have conflicting profiles running in setcpu
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
thisisreallygay said:
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
Click to expand...
Click to collapse
oh ok tainted is not vanilla
tainted IS sense with sense removed with vanilla remaning hence the word tainted
some sense is still there
i think
Yeah it's got sense contacts and stuff but vanilla messaging. But it has the sense dialer so I think it would also have lag with calls if the sense ones were having lag. And I just tested it and it took a lil while for it to recognize whose number it was but it still gave me plenty of time to answer the call. I'll be testing to see how it improves battery. Thanks for the find
Im also testing setcpu Advanced settings batery life (without performance loss)
What settings are those?
I (and several friends that I asked) noticed a mark increase in UI response (laginess) when coming out of sleep, opening app drawers, initializing the keyboards, scrolling between launcher screens, etc. Having random lags is annoying, but having 2-3 second lag spikes when using the keyboard is downright frustrating.
I know that lab benchmarks are way up with the new release, but frankly I don't care about those if my day-to-day functions suffer.
I first began to notice this when I made the stock upgrade to Froyo. 2 days ago, I flashed the EViO 1.5 ROM on my phone, and it seems to be 4x as bad. Paring down the window launcher helps marginally. ADW -> Sense -> Launcher Pro in order of most to least lag. I am currently using Launcher Pro just because it's responding a little better than the others.
In a somewhat related post, one of the developers offers that a lot of lag is due to aggressive garbage collection:
(unfortunately, I am not yet verified so I can't post the link)
I also wonder if the overhead from the JIT compiler or lack of proper memory caching isn't the culprit ... or perhaps this is to what the aggressive garbage collecting is referring.
Who else has noticed this? Can anyone offer up an explanation?
I would be willing to reflash to a new ROM if someone can suggest a custom ROM that they recommend as having faster normal UI response time.
Are you using Juice Defender or do you have off "always-on mobile network?" The lag when turning on the phone is the phone searching for 3G svcs, notice when you are on Wifi there is no lag
DirtyShroomz said:
Are you using Juice Defender or do you have off "always-on mobile network?" The lag when turning on the phone is the phone searching for 3G svcs, notice when you are on Wifi there is no lag
Click to expand...
Click to collapse
No juice defender.
I have my radio set to always on.
Most of my testing at home is done on AC power with WiFi turned on, lag definitely still exists.
There's a good 4 - 5 seconds of lag before I can use my window launcher after waking up my phone. I do have setCPU configured to scale the processor down to 245mhz while the screen is turned off. This may explain the lag after wakeup, but not the intermittent lag.
None of these issues using Myn's 2.2 rls3 Rom and ziggys 11/5 kernel. I DON'T use setcpu. It can cause instability issues. Like the lag time in wake up. Some phones don't like 245mhz when sleep. Try boosting to 384 screen off. Also, overclocking can be beneficial but clocking too high can cause poor responsiveness. It can also affect benchmarking scores negatively if clocked to high. Try ziggys 11/5 kernel, its doesn't support overclocking, but it honestly feels like it is overclocked using this Rom/kernel combo
Sent from my DAMN Evo!!
lag what lag ? my 6.1 is lag free
moodebony said:
No juice defender.
I have my radio set to always on.
Most of my testing at home is done on AC power with WiFi turned on, lag definitely still exists.
There's a good 4 - 5 seconds of lag before I can use my window launcher after waking up my phone. I do have setCPU configured to scale the processor down to 245mhz while the screen is turned off. This may explain the lag after wakeup, but not the intermittent lag.
Click to expand...
Click to collapse
If your setcpu governer is set on something like conservative, it can defintely cause intermittant lag. get away from setcpu and use a havs kernel.
Currently mine is instant, no lag at all, but I had this problem about a week ago. I am running Fresh 3.4.0.1 with Netarchy's 4.2.1 cfs/havs kernel.
What caused my problem with lag was a lack of internal memory. I was down to about 64 MB of internal memory left and it would lag on wake or when exiting apps, and I noticed that it would often have to reload the UI whenever I exited an app. The fix was easy. I moved what apps I could to the SD card and used titanium Backup to remove a bunch of stuff that I do not use. Once available internal memory was over about 100 MB (134 MB is what it was when I was finished) the lag totally went away.
Problem Partially Solved!
SetCPU was indeed the main culprit. I was under the impression that overclocking too much would just cause instability. It seems that moving the ceiling from 1228.8mhz down to 1113.6mhz solved most of my new lag issues with the EViO ROM.
Indeed, upping the screen-off throttle-down from 245 to 386 also seems to have helped the wake-up lag time, though I'm still doing some more testing on this one.
Would I need to set all floor values up to 386 as well, or is that just for the screen off value? What scaling setting do you guys in setCPU? Conservative? Performance? On-Demand? Does anyone happen to know exactly what the differences are in the algorithms that they use?
So can anyone offer up an explanation as to why overclocking would result in lag? Is there some kind of hardware throttle-down that's happening? I had a catch for if the battery got too hot that would throttle back to normal speed, but I never seemed to reach it. Is there a known heat limit where the hardware automatically throttles down?
As for the seemingly normal, random Froyo lag spikes, I'll be monitoring that over the next few days.
Thanks again in advance for any information.
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
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.