Happy holi guys
I flashed my rom regularly with 6 times a day
I am preparing script and tweak for battery + performance + tweak who itself adjust a cpu when doing CPU kinda work
Now problem arises below
i havent seen any degradation as once i have seen battery sucked. now i am sufering with serious problem one time i overclocked and its a time my cpu stucked at 902 mhz when i set to 806 mhz my device reboots itself and itself came to 902 battery is also good guys please help me if u can i want back to 800 mhz
Performance is also good no random reboots and none other problem. Why my cpu stucked at 902 mhz default
Help appriciated
the software which you used to overclock like setcpu is doing that setting at boot as you might checked set on boot option...
best option is connect to pc , go to recovery and uninstall setcpu or if you have created the recovery zip from setcpu you can use that too
madman_amit said:
the software which you used to overclock like setcpu is doing that setting at boot as you might checked set on boot option...
best option is connect to pc , go to recovery and uninstall setcpu or if you have created the recovery zip from setcpu you can use that too
Click to expand...
Click to collapse
Happy holi guys i tried this but my damn cpu stucked 902 whenever i changed my setting it itself came back to 902 mhz
Happy holi to you too
I have no idea about your problem but uninstalling setcpu might help or just flash a new kernel
A noob here
------------
May The Force Be With You
Well ... Might be the Script problem ... re-flash a new Script ... or reflash a new rom
that would solve ur problem ...
jumbobombo said:
Happy holi to you too
I have no idea about your problem but uninstalling setcpu might help or just flash a new kernel
A noob here
------------
May The Force Be With You
Click to expand...
Click to collapse
Yea the kernel reflash might workk
Sent from my GT-S5830 using xda premium
Related
Hi all, this is my first post, and i searched the forum with no luck. I have a CheckRom RevoHD V4 with the Siyah Kernel 2.6.1. The problem is that my screen won't wake up after some time that it's turned off. It doesn't happen always... it's seems a random behavior... The volume keys works because i can hear the sound of volume up and volume down, but the touchscreen, softkeys, power button and home button doesn't work at all and i can't get my home screen back. I need to remove the battery to reboot the GS2... I experienced this problem with te DarkNight kernel too. I tried to call my phone, i can hear the calling tone but the cellphone doesn't ring. I don't know if it's a rom related problem or it's a kernel problem. Hope someone can help me.
Ps: Sorry for my english
Hello I have a CheckRom v4 for my phone.i think that you to flash again with odin DarkNight kernel version 2.5.2 flash only kernel as a pda with odin
i tried to flash the new siyah kernel 2.6.4 trough CWM but not solved my problem... there is some difference between flashing trough odin an flashing trough CWM?
I have System Tuner for tweaking and set the kernel governor... i don't know if there is some incompatibility with this app and other apps like widgetlooker that need root permissions... really i don't know how i can solve this issue...
redirect11 said:
I have System Tuner for tweaking and set the kernel governor.
Click to expand...
Click to collapse
There you have your problem.
so are you sure that the problem it's related to system tuner?
redirect11 said:
so are you sure that the problem it's related to system tuner?
Click to expand...
Click to collapse
Probably. If you undervolt or underclock your phone to much, you wil get SOD's. That is basic knowlegde if you want to use those apps.
ah ok... but i don't use OC/UC or UV/OV... i only use this for change governors... but i have a question about SOD: the volume keys works in these cases? Cause mine works when display doesn't wakeup...
I'm having the same problem with this rom and kernel. I do not uv or oc. I left those settings alone.
It's really annoying and have left me missing calls because I cannot pick them up.
I'm having problems with my phone, when the screen turns off, it turns on again and I don't know what's happening... I previously changed timeout to 30 min because I was downloading stuff then I change it back to 30 s but now I have this issue. What should I do?
rolo143 said:
I'm having problems with my phone, when the screen turns off, it turns on again and I don't know what's happening... I previously changed timeout to 30 min because I was downloading stuff then I change it back to 30 s but now I have this issue. What should I do?
Click to expand...
Click to collapse
did you overclock your cpu and what rom/kernel are you using?
Raider_ said:
did you overclock your cpu and what rom/kernel are you using?
Click to expand...
Click to collapse
I have cyanogenmod 7.2 installed on my phone. The kernel is the one for this rom, i installed at the same time i installed this rom.
i dont know too much about overclocking but on cyanogenmod settings i selected "smartass". The default mode is "interactive" but i already tried switching between these and it doesn't solve the problem. the max overclock i think is at 1024. That's it
But the screen sometimes flashed and it's a little bit scary at times let me tell you because it is sleep and all of a sudden it turns on the screen, its like is possesed or something. xD
Can someone please help me? I thought the problem was solved but this issue is getting me out of my nerves, after the timeout screen goes off, the screen turns on again by itself for about 3 times. I don't know what to do, but it's draining battery because of this. Please help.
rolo143 said:
Can someone please help me? I thought the problem was solved but this issue is getting me out of my nerves, after the timeout screen goes off, the screen turns on again by itself for about 3 times. I don't know what to do, but it's draining battery because of this. Please help.
Click to expand...
Click to collapse
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
evilbarcode said:
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
Click to expand...
Click to collapse
Where can I change the scheduler option? I already tried wiping the dalvik cache and changing the governor to "ondemand" reboot, but the problem is still there, when the phone goes to sleep, it turns the screen on again about 5 or 6 times then it turns off and after a while it repeats.
evilbarcode said:
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
Click to expand...
Click to collapse
Raider_ said:
did you overclock your cpu and what rom/kernel are you using?
Click to expand...
Click to collapse
What has scheduler or governor or OC to do with this?
Sent from my Xperia Arc S using xda premium
The thing is I can't solve this problem, do you think if i reflash firmware and kernel it would be ok? But I dont want to lose my apps or data, and if I make a backup before reflashing then i restore it, would the problem come back? Please, I need to put an end to this thing, is driving me crazy!
EDIT: I attached a txt file with my logs. Using "aLogcat" app, I found this:
Maybe it can help..?
Does someone knows what is this about?
W/asset ( 346): deep redirect failure from 0x01030046 => 0x02080019, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x7f0d0008
if you see the logcat attached to my previous post, you see it repeats A LOT so I guess the problem is there but I don't know.... My screen is still turning on several times after going to sleep......I noticed a battery drain about 3% - 4% per hour so I don't think it's normal, when I go to sleep I have to have my phone on so the alarm sounds but for example I go sleep at 12:00 am and by the time i wake up 6:00 am in only 6 hours is about 15% or more drain..... I need to solve this problem
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
Hi,
I have rooted my HCL V1 tab and Installed "No Frill CPU Control" to use build-in governors.
After a day I found that If I used to reboot the device, the max frequency is set to 800 MHz rather the 1 GHz.
I don't know why it's is happening. As I had not flashed anything till yet and had only just rooted the device since i bought it.
I had also reset the device to factory setting but won't work.
So after reading so many threads I found the below things:
If I check my device:
Then the max speed at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
is == 1000000
But if I check this:
max speed at /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
then the value is 800000
for a while if I change this scaling to 1000000 then the device shows that its 1 GHz. But Now If I again reboot the device then check again and found that it's again 800MHz and the scaling value is again set to 800000.
May be this is not the correct thing on which I am thinking about.. So, Please help me. What should I do to get it resolved.????
Thanks in advance
flash it complete new!
JustInsAne aka CALIBAN666 said:
flash it complete new!
Click to expand...
Click to collapse
Hi,
I cant flash it.. I even don't have any custom recovery installed as I said in my thread. and I also don't have any backups yet.
So need a solution except flashing.
my first rule(for my self)i dont change anything without an backup or something.
Bhawan said:
Hi,
I have rooted my HCL V1 tab and Installed "No Frill CPU Control" to use build-in governors.
After a day I found that If I used to reboot the device, the max frequency is set to 800 MHz rather the 1 GHz.
I don't know why it's is happening. As I had not flashed anything till yet and had only just rooted the device since i bought it.
I had also reset the device to factory setting but won't work.
So after reading so many threads I found the below things:
If I check my device:
Then the max speed at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
is == 1000000
But if I check this:
max speed at /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
then the value is 800000
for a while if I change this scaling to 1000000 then the device shows that its 1 GHz. But Now If I again reboot the device then check again and found that it's again 800MHz and the scaling value is again set to 800000.
May be this is not the correct thing on which I am thinking about.. So, Please help me. What should I do to get it resolved.????
Thanks in advance
Click to expand...
Click to collapse
Please someone Help me.!!!
Yesterday my phone started to heat to much i checked the frequencies in kernel auditor and found them to be quite low i knew that they were thermal throttling so I left it and now my little cores won't turn on at they turn on for a sec or 2 and then turns off my performance had decreased as the second big core can also not getting turned on.
First try to lower the minimum frequency, then you can try to flash another kernel if you have unlocked bootloader and recovery installed.
gooomis said:
First try to lower the minimum frequency, then you can try to flash another kernel if you have unlocked bootloader and recovery installed.
Click to expand...
Click to collapse
That dudnt work man can anyone help???
gooomis said:
First try to lower the minimum frequency, then you can try to flash another kernel if you have unlocked bootloader and recovery installed.
Click to expand...
Click to collapse
I don't know about overheating, but disabling automatic applying the kernel settings after a reboot may solve the problem with cores not enabling.
Sent from Note 3, Xiaomi Redmi Note 3.
mr.loverlover said:
I don't know about overheating, but disabling automatic applying the kernel settings after a reboot may solve the problem with cores not enabling.
Sent from Note 3, Xiaomi Redmi Note 3.
Click to expand...
Click to collapse
Dude it's just not working I tried to disable the first little a53 ko and I found that it is not been disabled by any means on my rooted tab S2 and so it was the case with my redmi Note 3 also but now the a 53 Court is just disabled but now the kernel I think just automatically disabled the first a53 Core and doesn't let me turn on any other cores except one is a72 core which is very weird reboot clearing the Dalvik cache even performing a factory reset and I even tried to install nitrogen OS but it doesn't seem to fix the problem but my device was working a few days ago even last night it was just working fine but after that overheating issue that chip is not working I guess properly
It seems chip stopped working :/
I'd flash through edl latest global dev in miflash with option flash_all if I were you...then if problem persist you can be 100% sure its HW fault
Androbots said:
Dude it's just not working I tried to disable the first little a53 ko and I found that it is not been disabled by any means on my rooted tab S2 and so it was the case with my redmi Note 3 also but now the a 53 Court is just disabled but now the kernel I think just automatically disabled the first a53 Core and doesn't let me turn on any other cores except one is a72 core which is very weird reboot clearing the Dalvik cache even performing a factory reset and I even tried to install nitrogen OS but it doesn't seem to fix the problem but my device was working a few days ago even last night it was just working fine but after that overheating issue that chip is not working I guess properly
Click to expand...
Click to collapse
what I meant is disabling the master switch for CPU settings, so that they won't be applied after a reboot.
mr.loverlover said:
what I meant is disabling the master switch for CPU settings, so that they won't be applied after a reboot.
Click to expand...
Click to collapse
I am using stock rom without root and using cpu x to monitor the settings
Update:Kept it in freezer for 3hours and now its freezing cold and my is powering on and i am yet to see the cores
Update 2: cant believe my eyes the cores on again wooohooo!!!