Hi
Straight to the topic ?
Anyone find their CPU keeps getting back to Interactive after rebooting your phone?
Mine did that always, even if i set Adiutor to set some governor after boot?
Sometimes it wont even change the freq i had set, for example, if i set max freq to 1401, right after i press refresh then it will went back to 1094
The governor sometime stick to whatever i have set, but after rebooting the phone, it will always get back to Interactive.
I really like lionfish governor, please help if any of you wizard know how to?
Thank you in advance
You turn on set at boot yet?
i did for sure
most of the parameter i set went back to normal after rebooting the phone
Related
I followed the automated overclock instructions on running my Omap overclock automatically all the time with Memmaid. It seems to do just fine, but every so often, it all of a sudden reverts back to the stock speed of 180. Can anybody help me with what is going on?
Thanks!
Seems to happen when you manually put the device into standby with the power switch - if you automatically let it go into standby should never happen. But read all through the overclock thread you can read other users woes there - but i think this is often the cause.
Thanks Mark!
So how does it go into manual standby? Just by pressing the top power buttone once... or do you have to hold it down?
Anyway to disable that?
Download the program from this thread...
http://forum.xda-developers.com/viewtopic.php?t=41060
It has a feature to reset the overclock automatically after wakeup.
Kanjibankers said:
Thanks Mark!
So how does it go into manual standby? Just by pressing the top power buttone once... or do you have to hold it down?
Anyway to disable that?
Click to expand...
Click to collapse
Just by pressing once to put into manual standby, just let it do it on auto you be fine No way to disable it i know.
Hi.
This problem has been posted before, but there was no answer, that worked for me. I was wondering, whether anyone has found a fix in the meantime:
My MDA crashes almost every night when it's in standby and can't be woken up by pressing the POWER-button.
Sometimes, this even happens during the day when it's connected to the computer, goes to standby and then is disconnected.
Only a soft reset will solve the problem.
I don't really have that much software installed, especially no Today-screen plug-ins.
However, I had task switchers such as switch and tswitch installed, which didn't work for me and thus has been removed. I have the impression, that after uninstalling these, my problems started.
One of these - I don't recall which one - has a today plug-in which monitors battery and memory capacity.
However, it seems that programs on my MDA never get completely uninstalled. The unistaller always says that it can't completely uninstall the software and whether I'd like to remove the program from the list of programs installed. So what I did was clear the device manually... maybe that was a mistake...
Any thoughts on this?
sacha
I have exactly the same problem. First I had no battery charge and then after replacing the battery, I have this problem.
Any ideas please?
Is it a hardware fault and I need to return the device?
Cheers,
Joe
I have a same problem too, but until today i don't find any problem solving. Please help.
I've had exactly the same problem with my T-mobile MDA pro. I first returned it to the shop but the tech department could not find anything. Gradually the problem got worse; in the end it would not power-up at all and I had to perform a soft-reset each time. Even with only the factory default software running. Returned it the second time and got a new machine; problem solved. So it definitely is a hardware problem.
Could this be a battery problem?
This may be dumb, but ..........
This may be wildly off but I've had two problems that looked a bit like this with my XDA exec. Sometimes when I go walkabout with the wifi left on, even though I've switched off the pda, it will refuse to wake up afterwards. This has happened a few times, but never if I switched off the wifi before going on the move. I wondered if it was trying to connect and entering some hangup state. I have heard it beeping in my pocket as I walked past wifi points and it wakes up. Obviously it isn't consistent.
The other problem happened when I first got the pda while I was carrying it in trouser pockets with the on/off button exposed (ie not in the closed end of the leather cover. It appeared to be hung up and wouldn't wake up (apparently) but all that had happened was that the backlight had been switched off by an extended press on the on / off button. That may sound really stupid, but without the backlight in some lighting conditions the screen just appears dark. I sorted that one, by ensuring the end of the pda with the on / off switch is always in the pouch and safe from being squeezed in my trouser pocket.
Solution Found!!
its a problem with the voltage control Unit on the Mainboard. My solution for my Jasjar was to install Pocket Hack Master and then disabling the CPU scaling of the Bulverde in the settings. Before turning your unit off or closing the clamshell make sure the speed is underclocked at 312 mhz..you can always set it at 520 while using it. Hope this helps!!
clemsyn said:
Solution Found!!
its a problem with the voltage control Unit on the Mainboard. My solution for my Jasjar was to install Pocket Hack Master and then disabling the CPU scaling of the Bulverde in the settings. Before turning your unit off or closing the clamshell make sure the speed is underclocked at 312 mhz..you can always set it at 520 while using it. Hope this helps!!
Click to expand...
Click to collapse
same problem here. sometimes i just press meny meny times (very fast) the power button and the screen turns on. other times i have to soft reset.
clemsyn i'm not sure i understand your solution. do you say that every time i want to turn of the screen i have to start PHM before, and set the speed to 320?
if this is the solution, wouldn't it be very annoying?
I've got exactly the same Problem. I've already changed the battery, flashed Original Rom, WM6 and so on. The strange behaviour of my Mda Pro still exists. After a while, the Pro switches off (Standby-Mode) and most of the time, i can switch it on with pushing the Power-On-Button. But if the Pro stays in the Stand-By-Mode for a while, i cant't bring "him" back to me. Only a Hardreset works (most of the time, i have to put in the Power-Supply, otherwhise, only the red light flashes one time when i push the reset-button).
The problem first appears, when i flashed the original Rom to WM6 (with all steps i had to do: upgrade bootloader to 1.01 and so on). Downgrading to Bootloader 1.00 didn't solve the probs.
At this point, i'am a little bit confused.....i need help
P.S:
Hopefully, my first post is not the last one
Edit:
http://forum.xda-developers.com/showthread.php?t=267448&page=1
I've just read this Thread. Very good informations. So i'll try it with an original Battery...i will post my experience asap.
Not for me it worked
clemsyn said:
Solution Found!!
its a problem with the voltage control Unit on the Mainboard. My solution for my Jasjar was to install Pocket Hack Master and then disabling the CPU scaling of the Bulverde in the settings. Before turning your unit off or closing the clamshell make sure the speed is underclocked at 312 mhz..you can always set it at 520 while using it. Hope this helps!!
Click to expand...
Click to collapse
Hello Clemsyn,
I tried this with Pocket Hack master. First it worked and i started walking, and singing throough my house again.
And now, after a few days, it gives me the problems back. No difference if it is automatically set to standby or with the power button. sometimes I still need to reset.
Hack master gives an error when restarting, so I am sure it was switched on to this 312 speed and blocking the scaling of my Qtek.
I am tring to find a railway to put my head on!
Huib
I think we all have the same problem and no one has found the solution to it ? what a shame i-mate couldnt come up with a patch or upgraded ROM which will work hazzle free..
I have to soft reset everytime when my phone goes to standy mode and doesnt wake up.
I am sick of this **** , planning to sell my jasjar ....any takers ?not really here tho.
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
Anyone else having this problem. So far it's happened twice on me. I click the power button to lock the screen and then I come back to it a minute later and it's off. I try to turn it back on but it doesn't unless I remove and replace the battery.
I had this problem, even while running stock everything. The phone is very likely defective. I had to exchange it at the Sprint store.
I probably will do that if it happens more
Sent from my SPH-D700 using XDA App
Are you using SetCPU or anything like that? That happened to me one morning (because I set the minimum clock frequency too low: 100 MHz) and it wouldn't come back on save for a battery pull. I think the minimum safe frequency to prevent that from happening is around 400 MHz... but then there's no reason to have setCPU installed in the first place.
If that's not your case, then it's probably a defective phone, go and exchange it if that happens again.
Maybe related, maybe unrelated, but mine did the same thing after installing SetCPU and setting the profile to "OnDemand".
After actually reading the SetCPU info, it says on the Galaxy S phones the "OnDemand" will cause issues and you should use the "Conservative" setting to have it auto-scale the CPU to usage demand.
Swapped mine to that, and no issues since.
I've had this happen on occasion with an unresponsive program that is hogging the CPU. Mashing the power button repeatedly has little effect, so I just give it a few seconds, and try again. I don't think it has ever taken longer than 30 seconds to respond. Apps that can trigger this behavior include the AP News app, which is terribly-coded and even less responsive. Don't fault the device - it's just unresponsive software. As capable as the CPU and OS are, it's still possible to get a hangup like that.
Hey guys I have a rooted fascinate running jt1134 super clean done yesterday. Twice now since then the phone had shut down while idle. When I go to turn it on the phone doesn't respond. The only way to get it to come back to life is pulling the pulling the battery. Obviously something I did yesterday is causing it. Any ideas thanks...
Sent from my SCH-I500 using XDA App
Do you have SetCPU enabled at boot, or any active SetCPU profiles? My phone did the same thing when I used either of those features while on jt's clean.
Second the set CPU settings. I was having the same thing. I was trying to set profiles like I did on my D1 no go. I am still getting unable to auto detect after reboot, with no profiles. Nothing like learning it all over again.
I flashed this ROM this weekend and I'm loving the responsiveness of the kindle Fire now.
There is one problem I'm having with the device freezing when the charger or USB in plugged in and the screen is shut off. If I try to wake the device the back light comes on but that's it. I eventually have to reboot the device to get it working again. I've check the dev forum on this and have not seen any post related to this issue. I've also followed the instructions to a T, "Factory Reset", wipe "cache", "dalvik cache", and "system".
Has anyone else experienced this?
Reply
Disable screen animations for on/off. Set your cpu min value to 600.
Mythrilium said:
Disable screen animations for on/off. Set your cpu min value to 600.
Click to expand...
Click to collapse
By disabling screen animations for on/off solved my problem. However, I did not need to change min CPU value, currently set to 300.
Thanks for your help.
Also got this problem before, disable screen on animation works for me.
I still love that animation though xD