same here. how to solve it?boot to kernel logo, then reboot
Sent from my Xperia Ray using xda premium
Hhhmmmmm could be new feequency table. Ill have to have a look latersame here. how to solve it?
I edited my post. Got it working.Hhhmmmmm could be new feequency table. Ill have to have a look later
Sent from my GT-I9300 On Official JB
It's still there :crying:- Fixed Wifi issue
I have booted into the version 2 kernel a few times this morning. It almost always boots in fine. The few times that it didn't boot right in, was after heavy use of the phone so it was a little bit warm to the touch...then boot loop. I took the battery out and left the back off for a few minutes to cool off, then boots no problem....if you are impatient you can fan the back of the phone with the back cover off (the back cover actually makes a decent fan) while the kernel is booting, it may take a few boot cycles, but eventually it will get cool enough to boot (usually 2-3 boot cycles).Hhhmmmmm could be new feequency table. Ill have to have a look later
Sent from my GT-I9300 On Official JB
Can you tell me what you were doing when the wifi problem started, I can try and replicate it and get a logcat...tested then v2 kernel. the wifi problem still exist.
I wouldn't use 2016 MHz...the big issue you have with overclocking is the heat production. The heat will degrade the cpu and it will stop working. I am pretty sure that the phone will try and protect itself and when the cpu gets too warm it will shut off so you probably won't go from working device to brick in one go, but there will still be some damage done and sooner or later you will start having problems with stability and random FCs, even on stock ROM and sock kernel. Since the heat production is related to the power utilized by the cpu a better measure of "safety" is the Voltage applied to the cpu so one rule of thumb is to stop overclocking when your voltage table reaches 1200mV...typically around 1.4 -1.6 GHz on the Ray....i flashed the kernel n so far it works smooth as for my ray
n i manage to see that it can be OC up to 2016 MHz.is it ok if i OC my CPU over than 1.6 GHz? have you test it? coz,well you ive been reading the forum n even in 1.6 GHz they said it is risky enough
i using PA Rom btw
i see.so im using 1.6 GHz now.i hope its ok.thanks for sharing btw!I wouldn't use 2016 MHz...the big issue you have with overclocking is the heat production. The heat will degrade the cpu and it will stop working. I am pretty sure that the phone will try and protect itself and when the cpu gets too warm it will shut off so you probably won't go from working device to brick in one go, but there will still be some damage done and sooner or later you will start having problems with stability and random FCs, even on stock ROM and sock kernel. Since the heat production is related to the power utilized by the cpu a better measure of "safety" is the Voltage applied to the cpu so one rule of thumb is to stop overclocking when your voltage table reaches 1200mV...typically around 1.4 -1.6 GHz on the Ray....
The "best" will depend a lot on what you want out of it. The two best I/O schedulers are noop and sio. Depending on where you look one, will be ranked higher than the other so any difference is probably not that noticeable. You will notice a lot of differences with the different governors. There is a sticky on the ray homepage that describes the properties of the different governors. Smartassv2 is one of the most popular because it is supposed to give a good balance between performance and battery. Ondemand and Interactive put performance above battery and I think that Interactive is supposed to be the default Gov for JB....Conservative puts battery before performance but it will probably drive you nuts because it tends to lag as the cpufreq scales up...in my experience you will be able to undervolt more with Conservative than with something like Ondemand.i see.so im using 1.6 GHz now.i hope its ok.thanks for sharing btw!
may i know whats the best pair for I/O and governor? as for now im using smartassv2 and noop n it works incredibely awesome
yaa i read it already.thank you for you info though!The "best" will depend a lot on what you want out of it. The two best I/O schedulers are noop and sio. Depending on where you look one, will be ranked higher than the other so any difference is probably not that noticeable. You will notice a lot of differences with the different governors. There is a sticky on the ray homepage that describes the properties of the different governors. Smartassv2 is one of the most popular because it is supposed to give a good balance between performance and battery. Ondemand and Interactive put performance above battery and I think that Interactive is supposed to be the default Gov for JB....Conservative puts battery before performance but it will probably drive you nuts because it tends to lag as the cpufreq scales up...in my experience you will be able to undervolt more with Conservative than with something like Ondemand.
At the moment im looking into the problems with wifi on tiwlan cm kernels. There is problems also on ARC and PRO kernels once I get it sorted ill then release a newer versionWiFi stuck at Turning WiFi on... with FXP-146 CM10, and Nyandroid AOSP JB RELEASE1. I flashed the wifi modules v2 after a fresh insztall, and then again after a reboot, It didn't help. Please fix this bug because this kernel is considerably better for gaming then FlyKernel JB.