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
Related
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.
Recently, I've noticed that the Overclock settings in the bootmenu on my Defy+ only offer three clock speeds and three Vsel settings. It always used to have four. CPUSpy shows four clock settings: 300Mhz, 600Mhz, 800Mhz and 1000Mhz whereas the bootmenu only shows 300MHz, 600MHz and 1000MHz. Is anyone able to suggest how I might get the missing one back in the bootmenu?
I'm running bootmenu 1.1.8, as installed by Defy2ndint 2.3 (thus also recovery version 5.0.3.1).
SetVsel is no help because it causes the phone to reboot. I've had a look at this thread but the "fix" seems to involve changing quite a lot of stuff, not all of which seems to be particularly relevant to the CPU speed & voltage settings. In particular, it installs multiboot which I've always preferred to steer clear of, having no need for it (I'm a boring person who is quite happy with a largely stock ROM). Mind you, the touch bootmenu does look nice, though...
I also had a look at this single posting from the extensive CM7.1.0 thread. I've tried copying the overclock.conf and overclock.sh files from that posting on to my phone, but I still only get 3 CPU clock speeds showing in the bootmenu.
Anyone got any better ideas?
This title is so funny :laugh:
Which kernel are you using?
Froyo has got 3 settings gingerbread 4
I'm on Gingerbread.
I've got to the bottom of it: version 1.1.8 of bootmenu only supports three CPU speeds. I think that's because it's part of a Cyanogenmod release which is based on the Froyo kernel and therefore only supports three CPU speeds. I previously had version 1.1.0 which comes from somewhere else - I'm not sure where. I installed it, along with CWM recovery 5.0.3.4, from a zip file via recovery, but I can't now remember where the zip file came from. Fortunately I still had a copy of the zip file to hand, and re-installing it gave me back my 4 CPU speeds.
I'm still quite tempted to try that fix for SetVsel on Defy+, though...
ejstubbs said:
I'm on Gingerbread.
I've got to the bottom of it: version 1.1.8 of bootmenu only supports three CPU speeds. I think that's because it's part of a Cyanogenmod release which is based on the Froyo kernel and therefore only supports three CPU speeds. I previously had version 1.1.0 which comes from somewhere else - I'm not sure where. I installed it, along with CWM recovery 5.0.3.4, from a zip file via recovery, but I can't now remember where the zip file came from. Fortunately I still had a copy of the zip file to hand, and re-installing it gave me back my 4 CPU speeds.
I'm still quite tempted to try that fix for SetVsel on Defy+, though...
Click to expand...
Click to collapse
Install Jelly Bean! You will have latest...everything!
Sent from my MB525 using xda app-developers app
Now this is odd...
I installed the SetVsel fix, which included a lot of other stuff that I wasn't sure I wanted like touch bootmenu and multiboot. Anyway, it installed OK and SetVsel did work, but I decided I didn't like the rest of the baggage, and having got to the bottom of the missing fourth CPU speed in the bootmenu mystery, I didn't really need SetVsel. So I did a full CWM restore - of everything: system, data, recovery, bootmenu, the lot. And there I was, back where I expected to be...except that SetVsel still works! How did that happen?
So, I'm having this issue with my nexus 7, can't seem to find a post about this problem anywhere on the internet, much less XDA forums. Using SetCPU (Or Rom Toolbox Pro, or both at once with the same settings) I can't get overclocking or underclocking to work for long. The settings keep resetting themselves every time I turn the screen on and off, and every time I reboot the device. Yes, I always set the values on boot, and when powering back on I wait for the SU notification, but even both apps show the settings changed back to stock 1.3ghz.
I have tried doing this with stock 4.1.1, Glazed Jellybean 1.2; resetting the bootloader, recovery, and os back to stock and wiping out the sdcard; I have tried the stock kernel for underclocking; trinity kernel Clemsyn's elite kernel both the 1.8ghz and 1.5ghz for overclocking; and yet I keep on running into this problem.
If I keep the screen on the overclock settings stay, however if I underclock to 1.0ghz the cpu speed keeps jumping to 1.2ghz anyway.
So, anyone with any idea of what to do, or any overclocking experience, help would be appreciated.
Device: Nexus 7
Android versions tested: Stock Android 4.1.1 & Glazed Jellybean 1.2
Kernels tested: Stock, Trinity Kernel, Clemsyn's Elite Kernel 1.8ghz overclock & Clemsyn's Elite Kernel 1.5ghz overclock
Edit: Both supersu and superuser with updated binaries result in no change; updating busybox didn't help either.
SithDagger said:
So, I'm having this issue with my nexus 7, can't seem to find a post about this problem anywhere on the internet, much less XDA forums. Using SetCPU (Or Rom Toolbox Pro, or both at once with the same settings) I can't get overclocking or underclocking to work for long. The settings keep resetting themselves every time I turn the screen on and off, and every time I reboot the device. Yes, I always set the values on boot, and when powering back on I wait for the SU notification, but even both apps show the settings changed back to stock 1.3ghz.
I have tried doing this with stock 4.1.1, Glazed Jellybean 1.2; resetting the bootloader, recovery, and os back to stock and wiping out the sdcard; I have tried the stock kernel for underclocking; trinity kernel Clemsyn's elite kernel both the 1.8ghz and 1.5ghz for overclocking; and yet I keep on running into this problem.
So, anyone with any idea of what to do, or any overclocking experience, help would be appreciated.
Device: Nexus 7
Android versions tested: Stock Android 4.1.1 & Glazed Jellybean 1.2
Kernels tested: Stock, Trinity Kernel, Clemsyn's Elite Kernel 1.8ghz overclock & Clemsyn's Elite Kernel 1.5ghz overclock
Click to expand...
Click to collapse
are you using superuser or supersu? and is your busybox updated? heres a flashable supersu, flash it, boot, open the supersu app, update your su binaries if it asks. then get stericsons busybox updater free from the play store, open it, then update your busybox. reboot, then try ti set your cou speed.
simms22 said:
are you using superuser or supersu? and is your busybox updated? heres a flashable supersu, flash it, boot, open the supersu app, update your su binaries if it asks. then get stericsons busybox updater free from the play store, open it, then update your busybox. reboot, then try ti set your cou speed.
Click to expand...
Click to collapse
Using superuser, binary was updated earlier today, as was busybox, no changes after installing either of them.
SithDagger said:
Using superuser, binary was updated earlier today, as was busybox, no changes after installing either of them.
Click to expand...
Click to collapse
try supersu, superuser has had many issues with jelly bean.
simms22 said:
try supersu, superuser has had many issues with jelly bean.
Click to expand...
Click to collapse
Same results with supersu, weird stuff.
At least you got me to try supersu, looks much nicer than superuser does.
SithDagger said:
Same results with supersu, weird stuff.
At least you got me to try supersu, looks much nicer than superuser does.
Click to expand...
Click to collapse
you don't happen to have the trinity kernel toolbox?
simms22 said:
you don't happen to have the trinity kernel toolbox?
Click to expand...
Click to collapse
No, but I can go grab it with my play store credit if you think it will really help, I figured that most cpu controllers use the same system of controllers and such for setting cpu speed.
SithDagger said:
No, but I can go grab it with my play store credit if you think it will really help, I figured that most cpu controllers use the same system of controllers and such for setting cpu speed.
Click to expand...
Click to collapse
I'd hate to make you buy something, but if you do try it you'd have to uninstall setcpu. you can at least try it and return it if it doesn't work. you've got 15 minutes.
simms22 said:
I'd hate to make you buy something, but if you do try it you'd have to uninstall setcpu. you can at least try it and return it if it doesn't work. you've got 15 minutes.
Click to expand...
Click to collapse
Funny, I have been debating on buying trinity kernel toolbox for a few weeks not.
Well, I tried it out; rebooted thrice, left the screen of for over 3 minutes, the settings stick, my nexus7 is happily underclocked to 1.0ghz right now.
Now to restore my backup, and get a nice overclocking kernel going.
Thanks Simms!
SithDagger said:
Funny, I have been debating on buying trinity kernel toolbox for a few weeks not.
Well, I tried it out; rebooted thrice, left the screen of for over 3 minutes, the settings stick, my nexus7 is happily underclocked to 1.0ghz right now.
Now to restore my backup, and get a nice overclocking kernel going.
Thanks Simms!
Click to expand...
Click to collapse
sweeet
Im having the same issue
simms22 said:
sweeet
Click to expand...
Click to collapse
Afternoon All,
I'm looking for a little bit of guidance pls.
I've overclocked both my GS3 and my Nexus 7, but of reboot i loose my overclock as it sets back on default.
I've tried various apps to try and manage, incl STweaks and trinity, to no avail.
I have read its something to do with the Power HL (correct me if I'm wrong) but i can no longer find that post.
its doing my head in.
Any on got ant ideas pls?
thanks.
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.
Hi,
I just got my nexus 7 3 days ago.
I flashed TWRP and CM10.1.2, then the franco.kernel
Everything was going fine, until today it started to freeze when I select power off/reboot, while yesterday, everything was fine.
Any help?? (I can go into bootloader/recovery, by doing the combination)
I've tried re-flashing the franco kernel, and CM10.1.2.
Edit: I Fixed by under-clocking my GPU to stock settings (416 MHz), Before I Over-clocked it to 750 MHz
You can leave now
drew1ind said:
Hi,
I just got my nexus 7 3 days ago.
I flashed TWRP and CM10.1.2, then the franco.kernel
Everything was going fine, until today it started to freeze when I select power off/reboot, while yesterday, everything was fine.
Any help?? (I can go into bootloader/recovery, by doing the combination)
I've tried re-flashing the franco kernel, and CM10.1.2.
Click to expand...
Click to collapse
What exactly do you want help with? You can still transfer files onto your device and boot into recovery. Try a different ROM and/or kernel.
Username invalid said:
What exactly do you want help with? You can still transfer files onto your device and boot into recovery. Try a different ROM and/or kernel.
Click to expand...
Click to collapse
No thanks.
It turns out, it's because I've overclocked my GPU from 416 MHz to 750 MHz. It's fine now