Ive had the touchpad since the fire sales months and months ago. Had cm7 on it and went to cm9. I never had an issue with wifi or reboots. Ive been running unofficial nightlys since they came out and they were great. Now since the last month ive had issues with it rebooting...so i used Setcpu and put it up to 300...still rebooted...400...still rebooted..finally at 500 it reboots. What gives? My wifi has not been that great either but im not too concered about that disconnecting..just worried about the reboots because that will drain battery quick.
newtonfb said:
Ive had the touchpad since the fire sales months and months ago. Had cm7 on it and went to cm9. I never had an issue with wifi or reboots. Ive been running unofficial nightlys since they came out and they were great. Now since the last month ive had issues with it rebooting...so i used Setcpu and put it up to 300...still rebooted...400...still rebooted..finally at 500 it reboots. What gives? My wifi has not been that great either but im not too concered about that disconnecting..just worried about the reboots because that will drain battery quick.
Click to expand...
Click to collapse
I use Antutu CPU Master, 1.7 max, 384 min. Going to 500 min shouldn't kill battery too much more. I use webos quite a bit. It's a lot better on battery life.
Have you tried removing set CPU? Or see if it does it in WebOS?
Otherwise, I'm guessing it is defective in some way.
Sent from my PG86100 using XDA
What rom/kernel are you using? I was having this type of issue until I switched to the official CM9 nightlies, and now can set the min clock to 192mhz (or whatever the default min is)
I have it a 192/9xx mhz, no reboots whatsoever.
AOKP M5
Related
Does anybody know if it's safe to use SetCPU on the D2? The processor is fast enough. I'd just like to see if i can stretch the battery by underclocking it while the screen is off as I've read is commonplace on other phones. Thanks.
I would definitely like to know also cause if you can I would root right away
Sent from my DROID2 using XDA App
I rooted yesterday and setCPU was one of the first apps I installed - just for underclocking when asleep! Seems to have worked fine, no problems yet.
Yea I autodetected speeds and it seems fine. It won't allow you to overclock yet until we are able to either get a new kernel module to do it or a full kernel (bit off still, even droid x can't do that yet). I underclock when screen is off and that works just fine
ok. thanks. i've been running it for about 12 hours now to underclock with the screen off and so far, no issues. this phone is getting better by the day.
I've used SetCPU to underclock while the screen is off. My battery life is much better than before. I've also removed some of the bloat.
Sent from my DROID2 using XDA App
I too have been using SetCPU to underclock when the screen is off or when I'm in class. I haven't had any problems yet.
It's the first app that I've paid for but thats just because I'm cheap, but that's only because I'm a broke college student.
I'm running SetCPU 2.02 no problems. I'm actually running my phone underclocked to 800 and it's running fine. Screen off is set to 600.
Hei guys, I'm really, really new to this.
I've just flash andy's port of CM7 based on 2.3.4. I'm having a really though time with the battery, it goes down 50% faster than on my previous 2.2.2 official Froyo from LG.
Anyway, this question is about overclocking.
So, inside CM7 settings there's this "Performance" menu, in which you can go to "CPU", I've set there smartass governor, minimum 122 and maximum 768.
What does that mean? Does that mean I'm overclocking my CPU? Does it mean that smartass will allow or push the CPU to 768 when it's needed? Do I need to do something else in order to achieve that? (i.e - use get the CPU at 122 while screen off and increase it according to demand up to 768). - that's what I'm after.
Any response on the topic(s) much appreciated.
Thanks.
Regarding battery - calibrate it with the app from the market
Regarding OC - yes, when you'll use the phone your cpu will run at 768 mhz (note that you might get kernel panics). Your minimum speed is pretty low and it will take a little longer to get to 768... you will see some skips or lags.
Oh, and yes! You're overclocking and smartass will do what you're looking for (idle-122/in-use-768).
Sent from my LG-P500 using XDA Premium App
I would kick the min up to 480. That usually gives you a good balance.
Sent from my LG-P500 using XDA App
Thanks for the fast response.
As for the battery, I tried calibrating it and still the same.
I'm reporting 10% (exactly) each 2 hours, in idle, screen off, everything turned off except mobile data on EDGE.
At this rate, the phone goes dry in exactly 20 hours with minimal to no use. This isn't normal.
It heats up when charging (more than usual).
In battery stats I have all the four ones (android system, cell, etc.) at 25%.
No apps installed.
Just a few hours ago I tried replacing the stock kernel of andy's with the latest from franco (16) and zram.
Exactly the same.
I don't know what else to do, I already reflashed it twice. Same results. I can't post to the development forum just yet (not enough posts).
I guess I'll just go ahead and try mik's port... although I wouldn't want to, I love this one, everything works perfectly except the battery thing.
Did you use google maps?
"Known bugs
[...]
- Google Maps is eating your battery, kill this app after using in Setting->applications
[...]"
i think smartass does automatically change your cpu's frequency when you need it..but your minimum frequency is too low..change it to 320 Mhz....and are you using 3g all time..??
Yes, used google maps but killed it. Second reflash didn't even install it and still the same problem.
No, I didn't use 3g at all.
I only kept mobile data active on EDGE. and as I said, it was in idle. it's like the phone was used 24/7 even in idle.
and why is my cpu to low? the phone works like a charm with that frequency.
Check the 2 g networks only box in settings-networks- mobile networks....that may be the reason
Sent from my LG-P500 using XDA App
It's checked alright. Like I said, I used it on the EDGE (2G) networks.
Anyway this doesn't matter anymore since I've switched to mik's rom.
you can give void# forever a try too...gives me two days battery life on moderate use...
Okay, I will.
Is it safe to overclock the Touchpad using setcpu? I have it at 1.5 ghz and it seems to be working fine.
kscully said:
Is it safe to overclock the Touchpad using setcpu? I have it at 1.5 ghz and it seems to be working fine.
Click to expand...
Click to collapse
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Overclocking so far works well. I see no problems as of yet. Just make sure you OC with setcpu; frequencies do not show up in cmsettings when you try to OC there.
Sent from my HTC Glacier using XDA Premium App
atapia984 said:
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Click to expand...
Click to collapse
mines not overclocked and has happened 4 times today. So, obviously not an overclock only problem. I will tinker around with it, but ive yet to tell myself...man, this needs to be speedier. Its run QUICK. far quicker than WebOS and its many 10second pauses (OCed to 1.7 and patched to boot..)
atapia984 said:
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Click to expand...
Click to collapse
Haven't tested it yet, but some say it's a problem due to the "minimum cpu speed" setting when it goes to deep sleep. Something about it being too low and thus can't get out of sleep and setting the minimum higher (not sure of they value) should remedy that.
I'm using SetCpu with a OC of 1.5 and a minimum of 384 with no issues.
my question is should I click the box for set on boot?
i do. set on boot, min 384 max 1512, ondemand tcl
no sleep death, no lag, working great! (mind you im still on CM7 A1, by preference)
What is the difference between ondemand and ondemandtcl settings? Also, any problems encountered running 1.7g I've only read people running 1.5g...
There's a fix to the Sleep of Death issue and that worked for me. I thought using SetCPU caused the sleep problem but that doesn't seem to be the case. I'm going to see how far I can overclock my TouchPad now
link
I'm running Setcpu at 384/1.7 with zero problems.
I was having issues at first with failure to wake from sleep but after I changed my min to 384 It has not failed once. All my little problems went away when I made this change. Been running for 12 days without a single need to reboot.
butikofer08 said:
What is the difference between ondemand and ondemandtcl settings? Also, any problems encountered running 1.7g I've only read people running 1.5g...
Click to expand...
Click to collapse
i run 1.5 purely for performance/battery conservation but it goes to 1.7 just as easily too.
also traditionally:
Ondemand - Both CPU cores freely move up and down as needed.
Ondemandtcl - prefers the use of CPU0 unless CPU1 is absolutely necessary for use, then it will kick in. otherwise it will remain idle
does anyone try alpha 3?
I saw people said touchpad freeze when using setcpu. Does it work well?
im oc with 1728 max and 192 min ondemand. no issues or sleep of death. im thinking of bumping it up to 1.8ghz like i have in webos.
so...my note is rooted with OC and on CWM beta 3. i even have flashed a battery percentage status bar mod (after many tries and lots of FC's issues) i finally got everything stable on a stock rom oc'd at 1.8 and this thing was sick dude...i mean so fast and big and bright and perfect...no problems except for 1...was getting random reboots...3 a couple days ago while using boat browser every mtime so uninstalled and started using dolphin. worked great until 1 rando reboot today while on dolphin browser...i figure no big deal it happens when you tweak your phone...but then all of a sudden it did something different just now it did...it just randomly rebooted while toggling wifi on except after it booted back up i couldn't unlock the screen or get into the launcher and the screen went black and unresposive. power button did nothing even holding it down...i pulled the battery out and then back in and restart and phoone booted up normally. clear as a bell and lightning fast...
so i just dialed down the oc to 1700...hope it's all good though...can't think why it would do this...
thanks?
Your phone can't handle the 1.8 ghz overclock.
When overclocking, no 2 chipsets will perform the same. Some will be able to overclock to 1.8 and some will not.
zer0nine said:
Your phone can't handle the 1.8 ghz overclock.
When overclocking, no 2 chipsets will perform the same. Some will be able to overclock to 1.8 and some will not.
Click to expand...
Click to collapse
So then is this OK?
Well anyway I guess I'll post back with the results. Cuz I'm running that way now. Hope I don't brick this beauty.
All opinions welcome.
Sent from my SAMSUNG-SGH-I717 using xda premium
You won't brick by overclocking. If you run it at an unstable clockspeed for your phone, you'll just be getting constant reboots.
1782 mhz should be fine. Try benchmarking your phone using Quadrant and Antutu from the market to stress test your phone at that new CPU speed.
zer0nine said:
You won't brick by overclocking. If you run it at an unstable clockspeed for your phone, you'll just be getting constant reboots.
1782 mhz should be fine. Try benchmarking your phone using Quadrant and Antutu from the market to stress test your phone at that new CPU speed.
Click to expand...
Click to collapse
Thanks. I'm at 3723.....phone feels good.
Sent from my SAMSUNG-SGH-I717 using xda premium
yup, sounds like classic too-overclocked symptoms to me. Back it down a notch like you have already done and try again...
Hey everyone, long time not talk... Just curious, has anyone had any issues with their dual cores on their EVO V's? No matter what I try things won't stay stable.
The problem is one or both cores keep going back to the 384 default. Even when I loaded a butter sense kernel and had the min at 486 it still goes to the slower one. Either way I'll have the max at 1.5 or 1.2 and a lot of times when I'm waking it up, or other times when I'm just using it, like I said, one or both cores just plummet speed wise.
Right now I'm running NegaLite BluRom for the V and I haven't always had these problems. I read somewhere to not use any CPU managers but I still have any issues, and at least with the CPUM's I can confirm that the speed is way down.
Thoughts and or suggestions would be great.. If it's the ROM fine, but there aren't a lot out there for the V, and what is out there hasn't been updated in a bit...