search

HopelessFantasy / openetna

Automatically exported from code.google.com/p/openetna
0 stars 0 forks source link

SetCPU 2.x will cause unit to freeze intermittedly #407

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. install setCPU 2.x 
2. use it for a while 
3. switch unit sleep and wait for some time and turn it back on

What is the expected output? What do you see instead?
Expected to wake up and operational. 
Most of the time it end up frozen.( Home and Back button vibrates tho ...)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by justfort...@gmail.com on 12 Feb 2011 at 1:41

GoogleCodeExporter commented 9 years ago 
I'll assume you are using 6.3-rc6.

Please see issue 401.
I also use SetCpu2 sometimes.

My buttons do not respond so this is probably a different issue.
Could you please try a logcat when the phone is frozen?

Thank you

Original comment by trmfrei...@gmail.com on 12 Feb 2011 at 2:09

GoogleCodeExporter commented 9 years ago

Original comment by trmfrei...@gmail.com on 12 Feb 2011 at 2:20

GoogleCodeExporter commented 9 years ago 
Yes, I am using 6.3-rc6. In my case, it happen on all 6.x build.
I will try to do a logcat.
I need to figure out how first :P 
Lucky enough for me... hehe first time .

Original comment by justfort...@gmail.com on 12 Feb 2011 at 5:41

GoogleCodeExporter commented 9 years ago 
One thing to add, the phone seems to be ok if I use overclock widget.

Anyway, I will go do some digging on the logcat. I will report back asap

Original comment by justfort...@gmail.com on 12 Feb 2011 at 6:08

GoogleCodeExporter commented 9 years ago 
i'm using overclock widget - all is fine

Original comment by Fedo...@gmail.com on 12 Feb 2011 at 3:21

GoogleCodeExporter commented 9 years ago

Original comment by trmfrei...@gmail.com on 16 Feb 2011 at 11:41

GoogleCodeExporter commented 9 years ago 
Check if this still happens in 6.3rc7.

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 3:30

GoogleCodeExporter commented 9 years ago 
My phone rebooted possibly caused by setcpu.

There was no /dev/last_kmsg.

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 5:31

GoogleCodeExporter commented 9 years ago 
This is the kernel log after letting it sit after setting setcpu for 710mhz 
ondemand.
The reboot itself.

This could be caused by the phone not being able to handle 710.

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 6:09

Attachments:

GoogleCodeExporter commented 9 years ago 
The log is good, but the error seems quite generic. As any frequency past 528 
is not officially supported by the cpu, this seems like an hardware error.

Original comment by polyth...@gmail.com on 17 Feb 2011 at 6:25

GoogleCodeExporter commented 9 years ago 
Yeah, that is what I thought.

Perhaps the kernel should not allow 710.
Perhaps there should be a different version for higher than .... overclock.

I will try now with 650mhz and check if it happens again.

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 6:28

GoogleCodeExporter commented 9 years ago 
Actually, the kernel never goes over 528 Mhz by itself. The user must say so 
(by using SetCPU).
I see no problem in allowing 710 Mhz.

Original comment by polyth...@gmail.com on 17 Feb 2011 at 7:04

GoogleCodeExporter commented 9 years ago 
Ok.

I understand it.

But since OE is still unstable it could cause confusion because you cannot know 
if the user exceeded the CPU limits or if it is a valid crash.

Anyway, the phone appears to be stable at 650.

Original comment by trmfrei...@gmail.com on 17 Feb 2011 at 7:08

GoogleCodeExporter commented 9 years ago 
I would say we only accept bug reports where the cpu has not been overclocked 
(> 528Mhz).

Original comment by polyth...@gmail.com on 17 Feb 2011 at 8:22

GoogleCodeExporter commented 9 years ago 
Hi guys,

after installing the 6.3 rc7 and after selecting the "Detect CPU Frequencies" 
option, now I cannot even open SetCPU...

It shows the error message... «Sorry! The application SetCPU (....) has 
stopped unexpectedly. Please try again.»

Original comment by geeko.s...@gmail.com on 18 Feb 2011 at 11:49

GoogleCodeExporter commented 9 years ago 
i think i found the crashing bug

it s not related to setcpu
 i have the freeezing and hulting prblme with my phone, 1 week ago i flashed it again with rc7 with fastboot
i installed all the nessesery programs like setcpu2.10
and i had no crashesh and no freez
suddnely i realised that i dont use camera from flashing. and i used it
from the moment that i used the camera, crashing came back and i found my phone 
with emty battery(which means that it crashed during night) at the morning
till now i hd many many problems
i think the crashesh related to camera. and its bug dont fixed with reboot and 
need reflashing

Original comment by ali.fara...@gmail.com on 1 Mar 2011 at 7:32

GoogleCodeExporter commented 9 years ago 
I don't think this is related to the camera. I also have the crashes and i 
never used the camera in 6.3 rc7. I've reverted setCPU back to 528mhz. I will 
now wait and see if the problem persists

Original comment by amaury.l...@gmail.com on 8 Mar 2011 at 2:58

GoogleCodeExporter commented 9 years ago 
My phone crashes almost daily, I am not overclocking at all..
I just had 2 crashes in a row..within a 45 minute time span, this is the first 
time its ever happened. I am currently using the phone while its plugged in, I 
write a text message push send, it sends.. next thing I know I go look down at 
the screen and its frozen in place, no button work (no vibrating) screen lock 
doesnt turn off the screen and nothing is responsive.. This happens at least 
once a day during normal use, only solution is to remove the battery (and power 
cord when plugged in) this is in rc7.. does anyone else have this problem as 
frequently as me?? (I DO USE CPU TUNER, however the max my phone is ever set to 
is 528 mhz, and turns down to 246-480 on screen off profile..)

Original comment by cla...@gmail.com on 14 Mar 2011 at 10:36

GoogleCodeExporter commented 9 years ago 
My phone still crashes with setCPU at 710. But when i set it lower (like 691) 
the crashes are gone.

Original comment by amaury.l...@gmail.com on 15 Mar 2011 at 1:17

GoogleCodeExporter commented 9 years ago 
I uninstalled setCPU and CPU tuner, and have no overclocking or underclockin 
going on to the CPU, I still crash at LEAST once a day (just a screen freeze. 
cant do anything until the battery is removed.) does this not happen to anyone 
else? I heard something about sd card... im gonan remove it and see if this 
ever happens..

Original comment by cla...@gmail.com on 21 Mar 2011 at 7:54

GoogleCodeExporter commented 9 years ago 
ugg. no sd card. no cpu tuner. no set cpu. still get lockups. screen freezes. A 
LOT. just sits there and nothing works. no vibration from front buttons. lock 
button does nothing. nothing works until i pull battery.. ANYONE get this?? 
next time it happens when im at home I will do adb logcat and provide more info

Original comment by cla...@gmail.com on 21 Mar 2011 at 9:34

GoogleCodeExporter commented 9 years ago 
whats the best backup program? I want to wipe and reflash and see if this gets 
any better..

Original comment by cla...@gmail.com on 21 Mar 2011 at 9:36

GoogleCodeExporter commented 9 years ago 
i was using Mybackup but for some reason it was giving me errors about not 
being a r00ted phone when restoring the backups. I use Titanium now which seems 
to work very well. Are you using 6.1 or 6.3? I had this issue with 6.1 (RC5) 
and a fresh install got rid of the freezing.

Original comment by paulie...@gmail.com on 21 Mar 2011 at 11:00

GoogleCodeExporter commented 9 years ago 
6.3 rc7

Original comment by cla...@gmail.com on 21 Mar 2011 at 11:06