[Help][Chupachups 3.0] CPU/GPU Governors issues - G3 Q&A, Help & Troubleshooting

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

Related

Cannot use alternate kernel

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.

[Q] HenseMod 7: CPU overclocking

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.

[Q] Random reboots on Galaxy Nexus running JB 4.2.2

Hello. I'm running Cyanogenmod 10.1.0-RC5 on my maguro device, and franco-kernel r378. I've been experiencing random reboots, sometimes as often as 2-3 per hour. The phone doesn't even feel warm when it happens. Sometimes I'm using it, but sometimes it's just sitting there doing nothing and it reboots anyway. I've uploaded the last lines of my last_kmsg here, to see if any of you can help me figure out how to solve this annoying issue.
Thank you very much in advance!
Ivan.
I have the same setup no reboots. Do a clean install. Fix per,missions after installing Franco kernel. I have on demand and bfq. Stock speed' and don't use trickster mod
I did a clean install. I'm running the on-demand governor too, and 'deadline' instead of 'bfq' scheduler. I fixed permissions as well, I didn't change the CPU speeds, and I have no idea what the trickster mod is
I might add that i was having this same random reboot problem even with the CM stock kernel.
Any info from the last_kmsg file uploaded?
Thank you!
Best regards,
Ivan.
Small update: I did a fresh ROM install, again. I'm running the stock CM kernel, with the default parameters for CPU speed, scheduler and governor. The problem remains.
Please see an updated version of last_kmsg here.
Try to reflash stock. If the problem remains I am afraid it can even go worse. I mean reboots can become more frequent.
Did u changed your radio?
Had the same problem when I was on AOKP+Franco combo. Actually it was the radio for me which caused the problem.
Reflash everything, including radio, while returning to stock, it worked for me.
good luck :good:

d855 random freezes, then reboot (in all ROMs)

Hello people! I have strange problem.
Yesterday my phone freezes and rebooted, SIM was not working. I was on 30.3. 2106 cm nightly.
From that time, my phone randomly freezes and then immediately rebooted.
Before that, I was playing with CPU governor values, can that damage hardware? (No heat or something like that, but SIM)
Tried many cm13 builds, aosp's, fulmics, cloudy, another kernels, reflahed modem, another battery..
Every ROM was after clean install, apps installed from play store, few with restored data, tried with and without them, same with Xposed, doesn't matter anything.
Anyone know what is it? My phone leaving?
Sorry for bad English. Thanks David.
Tell us, which baseband version you have.
Only 21c on cm13 works. So this one.
OK, I had the same problem too.
I fixed it by removing Kernel Adiutor (yeah, Kernel Adiutor). Then I installed V21C (13.2-00002) modem and rpm/tz partitions (V21C too) posted by @Step-han right here.
I don't know how it works on cm but I'm using stock mm and it works good
Let's try it! I will post results
@jaro1221 It works! Thank you man! Maybe it was caused by installing Fulmics, which reflahed modem.
Thanks!
Having this same problem,first the sim not detected,then from a couple of days apparently random freezes and reboots that persist across stock based and aosp/cm Roms. But I noticed that the freezes and reboots occur only when the device is warm. Not hot,warm as in if the CPU temp is above 60�° C. If it is below 60, the phone can be used for hours without a problem. Any ideas? Could it be hardware related? I've used for months my g3 , and it rarely crossed the 70�° , and did not have this problem. I'm using a d855 16 GB if that matters.
Update: Just in case this could be useful for someone. First,my device got worse,it couldn't boot at all even while cold. it could not get past the lg logo,not in rom,not in recovery. I fixed my problem, maybe temporary, by using some folded aluminium foil. I opened the phone, and put some of it between the mother board and the display, in the same place where you can apply the thermal mod,and then some other between the board and the back case, under the place where the power and volume buttons are. I closed the phone and it booted up, I'm using it for half a day now, installed some games, played while monitoring the CPU temperature. It can go up to 70 degrees and it did not freeze,nor reboot as far. I rebooted some times myself to test if it would detect the sim card,and it had no problem so far,but maybe it is to soon to tell. So... I will update if something happens.

Unable to restore originals clocks

Hello there
Some times ago i was using an buggy firmware (OB17 if i remeber right) that caused battery drain. I proceeded to underclock the clusters to 1.3/1.0 GHZ via Kernel Adiutor
Now that the issue is fixed i want to go back to 2.15/1.6 because of lack of performance
But i can't ! On kernel adiutor, if i change the values, they are rested to 1.3/1.0 after i switch page or restart the app
I tested, it seems to be underpowed since i only score 2400 on geekbench...
I might need help
Thanks
Wipe data on kernel adiutor and reboot.

Categories

Resources