I installed CM7.1 but it constantly freezes/reboot. Flashed nightly 0308 but still the same problem. Overclocked to min 245 & max 710 ondemand. Please help
try lowering the overclock of the max cpu to something smaller it can be because of that your phone is rebooting in easier words your phone may not support 710mhz BUT if you have ticked set CPU on boot you will have to reflash the rom due to not being able to change the cpu settings manually
Kannibalism said:
try lowering the overclock of the max cpu to something smaller it can be because of that your phone is rebooting in easier words your phone may not support 710mhz BUT if you have ticked set CPU on boot you will have to reflash the rom due to not being able to change the cpu settings manually
Click to expand...
Click to collapse
U don't have to reflash. Just wipe data in recovery mode
Sent from my Blade using xda premium
Related
so im fairly new to android (converting from iphone) and bought myself a wildfire to check it out. So far ive used unrevoked to root and flashed the wildpuzzle ROM, now im attempting to overclock the processor. ive saved the 0163_768mhz_cpu_speed_v1.zip to my PC, copy to SD, installed from reboot menu and downloaded setCPU. But the max is still 528 mhz on setCPU :/ any ideas on where im going wrong?
If that is not working, first, flash the 0130 file (kernel), then try 0163. Also, if you flash 0130, you dont need 0163, and, can set the speed as you wish from within SetCPU.
Try it out.
BTW, I hope by "Installed from Reboot Menu" you mean entering into Recovery Mode, Selecting Install Zip from SDC, and selecting the particular Zip file.
One last thing, remember to take a Nandroid backup before flashing any overclockable kernels.
yes thats what i meant
I tried the 0130 file, had to unistall and re-install setCPU but is now running at 768mhz! thanks for the help 3xeno
That's great, but, just as an info, I would not recommend keeping it at 768. Most phones are unstable at that, and, performance actually drops. Try 710 or 729.
With the overclocking done, PSX4droid works well?
just some noob questions..
its my first time to flash a custom yesterday and i flashed cm7 #57..
main reason: i want my battery last and wana use openvpn..
last night, it freezes and reboot itself many times.
i think its because i set the cpu at 768
i wiped my WF again and flashed # 50 last night..
i just notice that my battery gets easily drain even i use setcpu, 245min 614max and some profiles...
what should i do then? do i need to wipe batt stat? if so,how to do that guys?
....
the next thing is i want the openvpn to got work and i cant find any tutorial how to do that..?
can someone help me? thanks in advance
sorry for my bad english
ijestan said:
just some noob questions..
its my first time to flash a custom yesterday and i flashed cm7 #57..
main reason: i want my battery last and wana use openvpn..
last night, it freezes and reboot itself many times.
i think its because i set the cpu at 768
i wiped my WF again and flashed # 50 last night..
i just notice that my battery gets easily drain even i use setcpu, 245min 614max and some profiles...
what should i do then? do i need to wipe batt stat? if so,how to do that guys?
....
the next thing is i want the openvpn to got work and i cant find any tutorial how to do that..?
can someone help me? thanks in advance
sorry for my bad english
Click to expand...
Click to collapse
well that happens to me also when i set my WF on 768...best set up for me (stable) is max 710 min 245...fast enough!
to conserve battery set your profile (set cpu) when screen is off to a lower frequency however, i suggest you use overclock widget as sometimes set cpu causes WF to freeze or hang up...then set your on screen and off screen speed...this will do the trick.
If your experiencing boot loop after flashing new nightlies probably its because of 4.2 kernel...try kernel 4.1 surely this will sort this problem out.
about vpn try to check main xda thread...i already pm you a link which might give you an idea where to start...
s0ulbl5d3 said:
well that happens to me also when i set my WF on 768...best set up for me (stable) is max 710 min 245...fast enough!
to conserve battery set your profile (set cpu) when screen is off to a lower frequency however, i suggest you use overclock widget as sometimes set cpu causes WF to freeze or hang up...then set your on screen and off screen speed...this will do the trick.
If your experiencing boot loop after flashing new nightlies probably its because of 4.2 kernel...try kernel 4.1 surely this will sort this problem out.
about vpn try to check main xda thread...i already pm you a link which might give you an idea where to start...
Click to expand...
Click to collapse
i installed kernel 4.1, full wipe.. phone opened (without bootflop)..
after 5 minutes, it loops again Boot Screen animation..
i backed up my #52
i flashed now CM 7 RC
there is nothing problem for now.. But statusbar icons are still bad..
than I flashed cm7_nightly49_inexussmatte_blackstatusbar ..
and looping in bootscreen
Now i am flashing RC again..
anyone knows an answer for Good Staturbar?
infectedtr said:
i flashed now CM 7 RC
there is nothing problem for now.. But statusbar icons are still bad..
than I flashed cm7_nightly49_inexussmatte_blackstatusbar ..
and looping in bootscreen
Now i am flashing RC again..
anyone knows an answer for Good Staturbar?
Click to expand...
Click to collapse
I updated it for RC1 btw.
I'm running the dual boot with phiremod 6.2 on SD. I tried to update the kernel to the 04242011 version and after setting OC to 1200 or 1300, it immediately freezes. I did the update from recovery and wiped cache and dalvik. Am I sol with a bum CPU?
Sent from my ADR6400L using XDA Premium App
after it froze up, did you try to just power down by holding the button, then just try to boot back up normally?
i've set my OC too high a few times back when i was first testing it out on my device and the same happened.
My NC can only handle up to 1100
But everytime i reflash a new kernel or build, i still try my luck with 1200 and it'll freeze up randomly then i just power down and reboot
djlim4 said:
after it froze up, did you try to just power down by holding the button, then just try to boot back up normally?
i've set my OC too high a few times back when i was first testing it out on my device and the same happened.
My NC can only handle up to 1100
But everytime i reflash a new kernel or build, i still try my luck with 1200 and it'll freeze up randomly then i just power down and reboot
Click to expand...
Click to collapse
Yup. So this is weird,i actually updated to phieremod test build then upgraded the kernel to 0618 and1200 works great.
Sent from my ADR6400L using XDA Premium App
My nook was freezing constantly at 1100, but never does as 1200. Might be a stepping issue.
Guys, what are the step by step instructions for installing MT Kernel 2.5?
I really cannot install it, I already tried flashing it via odin but my phone just crashes. Please help me guys.
Thank you in Advance guys!
Try mai77's method (flashing via CWM). It's in the second post of the kernel's thread (by ronnieryan). Make sure you've flashed to stock firmware first.
Sent from my GT-I9100 using xda app-developers app
I already did that. My phone just freezes in Samsung Galaxy Young Logo and after that, I cannot open the recovery mode.
Uhm, Is it recommended that I also include PIT and Bootloader in odin while flashing?
franzjonard said:
I already did that. My phone just freezes in Samsung Galaxy Young Logo and after that, I cannot open the recovery mode.
Uhm, Is it recommended that I also include PIT and Bootloader in odin while flashing?
Click to expand...
Click to collapse
Nope. NOT Recommended to use PIT/Bootloader/re-partition in odin.
Installing with ext4 system and cache could be tricky, Id recommend to flash to stock ROM before flashing the kernel.
1) Flash back to stock ROM
2) Go to recovery, flash CWM to get CWM recovery
3) Backup using backup and restore
4) Flash ext4converter.zip and reboot
5) Go to download mode
6) Flash the latest merruk kernel using odin
7) Now go to CWM, backup and restore -> Advanced restore -> Restore System
8) Wait till it completes
9) Reboot and your stock ROM will now boot
10) You can flash ANY custom ROM you wish and do any modifications.
Thats it, this worked for me
Oh thanks for the response. I already installed the kernel but I have a question. My galaxy y is having a random shutdown, do you know the reason why? And another question, what applications are you using to undervolt and to manage the cpu of your galaxy y?
franzjonard said:
Oh thanks for the response. I already installed the kernel but I have a question. My galaxy y is having a random shutdown, do you know the reason why? And another question, what applications are you using to undervolt and to manage the cpu of your galaxy y?
Click to expand...
Click to collapse
Same here, my phone does random reboot, too. I'm still in patience because the kernel hasn't been finished yet.
I'm using No-frills CPU Control to manage CPU and CPU spy to monitor it.
LilSasa said:
Same here, my phone does random reboot, too. I'm still in patience because the kernel hasn't been finished yet.
I'm using No-frills CPU Control to manage CPU and CPU spy to monitor it.
Click to expand...
Click to collapse
Oh, I thought it was just me that experiencing that problem. Anyway, thanks for the response.
franzjonard said:
Oh, I thought it was just me that experiencing that problem. Anyway, thanks for the response.
Click to expand...
Click to collapse
Hey, try setting your governor to ondemand (I was using ondemandx previously) and min. frequency to 312 MHz. My phone has lasted for nearly a day without rebooting, I just did it manually to update the kernel to developer edition version 8.
Guys just tick the option prevent other apps from changing the frequency in settings in No Frills CPU....
Because smtimes after deepsleep the phn frequency automaticalky changes to 156 mhz....
So it will not reboot automatically..
And keep its frequency greater than 312 to avoid frequent rebooting because armv6 processor supports frq greater than 300mhz....
Sent from my GT-S5360 using xda app-developers app
Guys, I already solved the auto shutdown problem. I reflashed the kernel because the first time I flashed it, I am on Merruk Kernel 2.0 Pre-final. Now I flashed it on stock. I got it solved and I set 312 Mhz minimum on no frills using smartassv2 and vr.
By the way, I will flash the version 8 now.
Ive recently flashed the latest 4.3 ROM from Quarx. (previously I was using an old version of the 4.1 ROM from Quarx too).
First it was _really_ slow, after a while I figured out, that the CPU was reporting 0MHz maximum and 300 MHz minimum. The problem was, that the CPU speeds were in the bootmenu 300,600,1000,1000. To fix it, ive changed it to 300, 600, 800, 1000.
Now the phone is super fast, but I think there is some problem with the CPU speeds. If the screen is off, it runs at 300, but if I turn the screen on it will always run at 1000 - even if the CPU load is like 10%. Ive tried boosted and smartass governors, stock and lower Vsel values, no help.
Is this normal? If not how can I fix it?
thanks
Strange. It shouldn't be stuck to 1000 when screen is on, in fact it should increase to 1000 when there is some interaction. Try starting fresh.
Sent from my MB526 using xda app-developers app
syddd said:
Ive recently flashed the latest 4.3 ROM from Quarx. (previously I was using an old version of the 4.1 ROM from Quarx too).
First it was _really_ slow, after a while I figured out, that the CPU was reporting 0MHz maximum and 300 MHz minimum. The problem was, that the CPU speeds were in the bootmenu 300,600,1000,1000. To fix it, ive changed it to 300, 600, 800, 1000.
Now the phone is super fast, but I think there is some problem with the CPU speeds. If the screen is off, it runs at 300, but if I turn the screen on it will always run at 1000 - even if the CPU load is like 10%. Ive tried boosted and smartass governors, stock and lower Vsel values, no help.
Is this normal? If not how can I fix it?
thanks
Click to expand...
Click to collapse
Did you flash with 08.01 or with 09.17 rom?
I tried both and only 08.01 is working fine for me, I had problems with the 09.17 ( My hardware buttons didn't work right....)
andy-q said:
Did you flash with 08.01 or with 09.17 rom?
I tried both and only 08.01 is working fine for me, I had problems with the 09.17 ( My hardware buttons didn't work right....)
Click to expand...
Click to collapse
If hardware buttons didn't work, it is usually indicative of a full system partition/wrong gapps/too big zip.
hotdog125 said:
Strange. It shouldn't be stuck to 1000 when screen is on, in fact it should increase to 1000 when there is some interaction. Try starting fresh.
Click to expand...
Click to collapse
Will these steps result in a complete reinstallation? Ive backed up all data from the phone, so I can wipe everything.
Copy the zip file to your SD card.
Reboot and enter recovery.
Wipe cache + wipe data + wipe dalvik cache.
Install the zip file from the SD card.
Wipe cache + dalvik cache again
Or do I need to do something else for Quarx's latest ROM? like install a different SBF or kernel? Ive rooted (and flashed an .sbf) this phone like 2 years ago.. Before 4.3 I was using a 4.1 build for a long time.
You need to flash a new 4.1 build which has TWRP and then flash 4.3, because the old CWM binary does not support 4.3. I suggest you do a full wipe with defy full wiper or AROMA wiper.
Sent from my MB526 using xda app-developers app