hello people, i am having problems with my galaxy player 5.0 freezing up
i am using the cm 9 rom found here: http://forum.xda-developers.com/showthread.php?t=1679957
heres my problem first off my cpu it is overclocking on its own and i dont want it to since it harms my device's life span i can set it to the stock setting (1000 ghz) but when i go in after a while it will show up at 1200 cpu so id like to know what is up with that?
know to problem im having some of my apps will not boot up it will start to go in but it will not load into it it will freeze and after a bit it will come up " not responding do you want to close the program" it is really bugging me i ca nstill go back to my home but it takes a while and a few trys before going into the game
could this be an unsuccesful overclocking
by the way i have the us version with this kernel http://forum.xda-developers.com/showthread.php?t=1445840 and this file (DD_01142012.tar)
it also freezes in the middle of one of my game (dream heights) is it the app or my device
some answers would really be appreciated
i will thank the people who respond with helpful replies:good:
You are not actually running entropy's kernel. cm9 comes with a kernel that is flashed along with the rom.
your overclock settings will not stay unless you tick the set on boot option.
you may want to do a full wipe/ reflash rom, or try cm10
Related
Hi
Got a major problem, I hope someone can help?
Basically I have intalled the Phantom f4 Kernal, and overclocked it.
Its been ok.
However today I did a full reset, now it wont fully boot.
it gets to the Bootup screen, then stops on:
MSM_timer_set_next_event (16) alarm expired etc
Please help .
have had no sucess with reboots, however I can get the usb operational, however webos doctor cant help.
thanks,
W
I had a problem with kernel F4 too (don't know if the kernel caused that), but my TouchPad couldn't boot at all (of course the PC can't recognize it). I tried many ways to turn it on but no luck. However after 30 min, I can turn it on and make a full hard reset. Everything seem ok now but need more time to say something about the kernel
Boot it into the download mode, then just use webOS Doctor. Samething happend to mine. Its an easy fix though.
Don't use beta kernels if you don't know how to Doctor your TP. They're pretty clear about this when you sign up for the testing feeds.
Unless your running benchmark tests which mean nothing in the real world , I bet you can not tell the difference between uberkernel clocked at 1.5 and the alpha and beta kernels clocked at 1.8. As an extra bonus uberkernel is stable. Crazy...but if you don't know what you are doing quit screwing around in the testing feeds and then crying when you cant fix it.
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
benoitm974 said:
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
Click to expand...
Click to collapse
I have same problem in zombie panic kernel v 1.59 and v 1.61.
after i update to v 1.62, i don't had problem reboots. and everything it's ok.
Problem occurs usually when:
I use the phone for 10/15 minutes, that is running music or radio, or using the phone, like surfing and installing app from market.
I'll try the new 1.63 ...
Benoit
Sent from my U20i using xda premium
Hi, No reboots for me 4 days into 1.63+2.1, I did similar process only difference is I use clockworkmod, someone else will have to confirm but I remember a while back all the roms where coming out with "no longer supporting xrecovery". As said dont know might be nothing but everyone seems to use clockworkmod now for flashing.
Sorry assuming you used xrecovery to flash rom since you mention installing it.
Well strangely, the update to 1.63 did it, no more reboot and I can even OC the phone ! It works great no reboot, even with wavy usage of GPS navigation with CoPilot live over the week end ! this is perfect !
I only have an issue with the radio FM app which is buggy : sound start on the hp instead of head phone, favorite station are not kept, frequencies are written in green on black which is not visible and RDS name is overlapping frequencies ...
Another issue, I'm still not able to fine tune auto brightness to have good reactivity when phone get out of standb by on shiny day it take 1/ 1.5 second for the screen to detect it need to boost lightness ... Same when I'm in a call and I want to use the keyboard to dial, it takes 1/1.5 second for the phone to adjust brightness... I've tried several tutorial from forum but it still have this small lag in brightness reactivity.
Other the phone is now perfect to me in 2.3.5 ! Thanks very much slade87 ! One note I don't like the boot animation some less shiny would have been welcome ...
Cool you got it all working, yes there where instabilities with cross ROM/kernels.
I like the new bootanimation but you can allways change it out if you dont..
(update 7/7/11)[Boot Animation]more bootanim
Bootanimation Installer v3.3
I have an LG Optimus Me P350. It is supposed to have a processor of 600MHz. I have it rooted and running Cyanogenmod 7. I have put SetCPU in it as the native overclocking support in CM7 does not work. Whenever I change the settings the phone shuts down after a few minutes. And it always shows 275MHz or something like this. The phone is really slow and takes years to load anything. HELP!!
New kernel and rom
Try to install a new rom and a new kernel;-)
Let me first explain what I did.
1. From stock rom, after doing the root (TWRP recovery), i flashed JellyDaemon v 2.0 listed here http://forum.xda-developers.com/showthread.php?t=2307247 . Used CPU control inbuilt in app to set CPU governer to OnDemand
Fantastic ROM with no problems.
2. After the news of 4.2.1 release came, I started looking for 4.2.1 based roms. I went with StarkHD listed here http://forum.xda-developers.com/showthread.php?t=2212028 . I think my download went wrong and file wasn't downloaded cleanly. I flashed with it. Flash went on successful. Phone got hung at the boot animation. Tried multiple methods to start the ROM. No success. Phone not booting into any ROM.
3. I had stock rom v 0.16 available with so flashed it with SP flash tools. Flash was successful.
4. Downloaded Naturewiz HD listed here http://forum.xda-developers.com/showthread.php?t=2319288 . ROM flashed and phone booted. Restored the apps. Used battery calibration app to calibrate the battery. After this, noticed that every time phone went into standby, it won't wake after that and needed reboot. I thought it to be bug in the rom.
5. Downloaded 4.2.1 based rom listed here http://forum.xda-developers.com/showthread.php?t=2306461 and flashed it. Flash was successful followed by successful TP upgrade. Installed everything. Same problem noticed. Phone won't wake from standby. Needed to be rebooted.
6. I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Any solutions to this? There are no other problems I am facing.
"I figured it to be a CPU governer problem left over from JellyDaemon v. 2.0. So installed juice defender and set the CPU governer to OnDemand. Frequency of reboots has reduced but the problem still persists.
Problem: The phone does not wake up when put to standby for a duration of 2-3 hours.
Click to expand...
Click to collapse
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Sent from my CaNvAs HD using xda-developer app.
adizrox said:
Looks like you yourself gave an answer to your problem. Don't enable Ondemand. if you still getting the problem. take a video of your problem and try posting along with a link to the video (I am not sure whether it is allowed). this way it will be easy to know what the problem is... hope i helped..
Click to expand...
Click to collapse
Thanks for your reply. I will try your suggestion and see. In the meanwhile, I removed TWRP and flashed CWM 6.0.3.0 and fixed permissions with that. The phone did not reboot on its own for close to eight hours (which it was doing earlier at random). I thought problem was solved. But trying to go through contacts list (DW Contacts), phone rebooted on its own.
Can anyone tell me a method where you do a clean install and bring the phone to a factory fresh state. Something similar to tutorial by team overcome for galaxy tab. Frankly, that seems to be the only possible solution: Get the phone in a completely formatted factory fresh state and then install any other ROM.
SP flash tools
To get your phone to a default factory status. you have to flash the original rom using SP tools. Links to both can be found in the forum.
Finally, tired after numerous attempts, decided to take it to the service center. Asked them to update to 4.2.1. They had the same problem. After flashing, the phone just wouldn't boot past the boot animation.
They kept trying. After two hours, they gave it back to me saying there is a hardware problem which requires a main board change.
I had suspected all along and now I know I was right. I asked them about the time line. The answer I got was even more shocking. Minimum two weeks, but there are lots of hand sets awaiting main board since more than a month
I guess I am better off with current status (Ver .20 installed and rooted).
Seriously, this episode has seriously dented my faith in micromax as a brand. One can buy there phones and be happy with whatever has been packaged. Trying anything new can be dangerous.
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
It's probably a software issue, JB has tons of bugs. What kinda advise do you want? You need to re-install the rom (and clear cache ofc) and if that doesn't work re-install the stock rom via odin and then install neatrom if you want. And just don't use power save mode until you get an update? It's useless anyway... You can also try another kernel, this seems like a kernel problem.
Power saving actually just have a few advantages like turning of un-needed things like haptic feedback and some other stuff which you could do manually, and the main power saving feature is that it limits the CPU to use only 800Mhz max, this might be having some issues with Apollo kernel (as it works fine with stock or stock based kernel like Philz), but Apollo is a powerful kernel and will let you manually adjust the CPU limits even at your preferred limits manually, so if you want to save battery just manually adjust the settings instead of using Power Saving mode.
Sent from my GT-I9100 using Tapatalk
Perphide said:
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
Click to expand...
Click to collapse
It may be a bug in that rom. try another rom
Thank you!
Thank all of you for the help and advise!
I will no longer use the powersafe feature and start using the Apolo kernel again, since that kernel gave me the best battery life.
It might have been a coincidence of course that my S2 died/didn't want to start up no more shortly after using the powersafe feature... however from all of the above advise it seems that I don't need that feature anyway so I feel safe to switch back to the Apolo kernel again with my new installed NeatROM SuperLite 2.4.
If the problem returns I'll be here to post it, it might still be a bug in the Apolo kernel of the NeatROM ... I am not sure. Time will tell, or not if it had to do with the powersafe feature which I won't be using any more.
Thank you all!