Hey guys, little issue that I can't figure out.
If I flash a rom with a kernel included of course I do not have any issues.
As soon as I try changing the kernel this is where I have issues.
The issue is that when I turn the screen off and the phone sleeps, after about 5 minutes it will not wake back up. I have to do a battery pull and eventually reflash the rom due to improper shut down/corrupt file system.
I have even tried flashing the rom and the kernel in the same recovery session to no avail.
I wipe cache and dalvik any time I flash something.
Running SRF 1.1.0 and have tried numerous kernels including twilight and genocide.
Did this also on SRF 1.0.2
Does your screen flash during the kernel flash process? It should show blue letters.
063_XOBX said:
Does your screen flash during the kernel flash process? It should show blue letters.
Click to expand...
Click to collapse
Yes it flashes and shows the random misplaced words. The kernels flash just fine but they all give me the screen of death after sleeping for 5 minutes or so.
Are you doing any over/underclocking using SetCPU or Overclock widget?
063_XOBX said:
Are you doing any over/underclocking using SetCPU or Overclock widget?
Click to expand...
Click to collapse
No, it will do it without changing anything. I do not have to even have setcpu or anything installed.
Then I think it might simply be that you have one of the poorer quality processors that don't handle undervolting well.
or its set to 100 as low and some phones dont wake from that...get setcpu and change it to 200 - whatever...or /system/etc/init.d and edit the 24-cpufreq file..
scroll down and it should say
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governer
Here you can change the governer..from conservative to on-demand wtvr..
and here:
#echo "100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
change the "100000" to "200000" and your phone should have no problem waking.. you can also overclock (if the kernel has the options) by changing the lines above:
#echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
change "1000000" to "1200000" or the freq you want and kernel can achieve..
I have tried installing setcpu and setting minimum to 200mhz, tried conservative and ondemand with same results.
I have 1 time successfully ran vision kernel. Even at 1.4ghz it ran fine for 3 days.
Isn't the default with SRF already underclocked? It runs fine on the default kernel.
I was having the same issues as you as well. I ODIN'd back to EB13, rooted using CWM 2.5.5, stayed on RFS, and I haven't experienced that issue yet. I am currently running the Viper 5.0 ROM. Performance isn't where I would like it, but it's running fine. I wonder if it is an EXT4 issue on some phones.
Related
I have a HTC Desire with SLCD screen, HBOOT 0.93, Starburst Lite 1.2.0 ROM and flashed Data2Whatever v0.4d with a 1280Mb Ext3 partition.
(I konw I should have used the Data2SD Installer given in Starburst but I forgot.)
After the installation everything was fine, including installing and launching apps, and rebooting.
But on one boot I installed SetCPU and overclocked the CPU to 1190 MHz on smartass scaling. Rebooting was OK, but once I changed another SIM, and when I boot into the system I can't light up the screen, although when I pressed the sleep/wake button the keys did light up.
Then I reflashed the ROm and Data2Whatever and tried changing SIM and reboot without installing SetCPU, and there was no such issue. However, once I installed SetCPU, the same problem occured again. I've tried 3 times or 4 and got the same issue with SetCPU every time.
Does anyone have the same problem as I do? If there really is a problem, what should I do if I want to overclock?
Many thanks!
Sadly there is nothing you can do much. Overclocking a CPU, especially in a phone does not always work. What something works for some people won't necessarily work for you. You could try dropping it to 1113MHz since that is stable, but anything above that and it starts to get a little shakey.
would agree with the previous post, 1190 MHz is not stable for everybody, try overclocking to 1113 MHz (even though i'm not sure y do u need to overclock)
I foolishly set my kernel to OC to the max in CM7, with "Set at boot" checked (stupid, stupid, stupid...), and now LPP keeps crashing on boot, so I am unable to get to Performance Settings to reset the clock speed. I was running the Tiamat kernel at the time, but have since flashed stock over it to no avail.
Short of a full wipe, what can I do to get my CPU back to a more sane speed? I haven't done a full TiBackup in a few days, so I'd like to avoid the nuclear option if I can.
Try booting it in safe mode.
Hold the menu button while you turn the device on. (I think that's how you do it.)
It should let you fix SetCPU.
godsmacked4653 said:
Try booting it in safe mode.
Hold the menu button while you turn the device on. (I think that's how you do it.)
It should let you fix SetCPU.
Click to expand...
Click to collapse
I wasn't using SetCPU; I was using the Performance Settings within CM7. And as it turns out, my problems weren't related to overclocking: I was running at 998MHz once I flashed back to the stock kernel.
Regardless, I ended up being able to get into TiBackup to get an up-to-date backup set, then wiped and reinstalled. Much better now.
My phone is R800i, -64 baseband, running the KA11 v2 ROM with DooMKernel.
I have SetCPU which works a treat. Overclocks / underclocks fine.
My problem is, every time I reboot the phone, it reverts back to the ondemand governor. I change it to Performance governor every time, but this becomes annoying.
I have no idea why. I read on another thread that the newer superuser app doesn't give root access to SetCPU early enough when booting? I have "set on boot" ticked.
Any suggestions?
My version of SetCPU is 2.3.0
Superuser v3.0.7 (41)
Su binary v3.0.3.2
Try no frills. I know that I had problems when rebooting the phone. It wouldn't set properly. Something about an improper shutdown.
Powering off and back on rather than rebooting would apply the changes properly for me.
I say try no frills because it will tell you if the settings have been applied. Not sure if SetCPU will tell you or not.
Never found a fix for it though.
Hi,
I'm currently using ROM HenseMod 7, apart from SMS issue it's working well.
But I'm having trouble with No-frills CPU which was included in the ROM. Every time I try to change CPU values the phone reboots. Even if I check "apply on boot" button. I also tried ROM Toolbox Pro app and it's the same story.
Am I doing something wrong or missing something?
Thanks.
Weird. What if you backup your apps and reinstall the ROM? Make sure you make a backup in cwm.
First I tried the Themed version of HenseMod - but then I changed it to the other one - the results were the same, when I changed the values and confirmed them, phone rebooted after few seconds. I set 768 Mhz as maximum. The only thing I can change is governor.
Born2B said:
First I tried the Themed version of HenseMod - but then I changed it to the other one - the results were the same, when I changed the values and confirmed them, phone rebooted after few seconds. I set 768 Mhz as maximum. The only thing I can change is governor.
Click to expand...
Click to collapse
Try a new kernel?
I'm not the Only one with the Problem? Yea. I have this too. Every time I try (maybe you too) to Overclock over 600MHz it will Reboot. Tried every Kernel I found.
Video about the Issue
So here is my problem...
Since Chupachups Rom updated to 3.0, I've been experiencing problems about the kernel control (both with stock and skin1980's own kernel) using Trickster Mod.
I just can't seem to set and lock CPU/GPU frequencies
I did check the kernel settings to set them on boot, but there isn't the issue; when I choose and set a frequency, upon tapping on the tick, the frequency immediately jumps back to the previous one (Which strangely forces itself at around 1.1Ghz-1.9Ghz for max freq and sometimes 960Mhz for Min freq)
As for the GPU it sometimes underclocks itself.
I was wondering it could be just a read bug, or something else.
I tried by a fresh flashing but still the issue is here.The .zips I flashed though are:
The rom itself
Kickoff's updated Lollipop theme
skin1980's kernel
Oversharpening Script
The oversharpening script also seems to lose and set the value to 0 after a while when I picked other values (ex: 28) (the UI seems as blurry as when I set it to 0 since the beginning.)
Try reflashing rom and kernel. I am on CC 3 and everythings fine.
And, do you really need that oversharpening fix? You really see the difference after?
DelBoy said:
Try reflashing rom and kernel. I am on CC 3 and everythings fine.
And, do you really need that oversharpening fix? You really see the difference after?
Click to expand...
Click to collapse
The updatedLollipop theme removes the oversharpening (I think?)...
You don' know many times I flashed, format my phone... I'm losing hope (I even went back to Kitkat and start all other again) I format my internal SD, etc