Hello everyone, Today I wanted to upgrade my SGS2 Dark Kinght with kernel 2.3 and 3.1.1 to CheckROM RevoHD CheckROM RevoHD4 and after restoring all no problem except that now BLN Control Pro first start I said that was not then I can turn it reinstalled the kernel, I have to reboot and I also enabled the notification option activated flashing just do not work when I get the mess that I do not read the buttons do not light. What can be the first premise that everything worked perfectly??
Related
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
benoitm974 said:
Hi all,
I can't post on development, just wanted to thanks slide for Gintonic 2.1 & new kernel performance is up, yet i still experience random reboots on my X10 mini pro.
what I did: SEupdate, format SDcard, then root & xrecovery, then reset/wipe and install rom & kernel, so I'm sure it's clean install.
But I'm still experiencing reboots ...
Regards,
Benoit
Click to expand...
Click to collapse
I have same problem in zombie panic kernel v 1.59 and v 1.61.
after i update to v 1.62, i don't had problem reboots. and everything it's ok.
Problem occurs usually when:
I use the phone for 10/15 minutes, that is running music or radio, or using the phone, like surfing and installing app from market.
I'll try the new 1.63 ...
Benoit
Sent from my U20i using xda premium
Hi, No reboots for me 4 days into 1.63+2.1, I did similar process only difference is I use clockworkmod, someone else will have to confirm but I remember a while back all the roms where coming out with "no longer supporting xrecovery". As said dont know might be nothing but everyone seems to use clockworkmod now for flashing.
Sorry assuming you used xrecovery to flash rom since you mention installing it.
Well strangely, the update to 1.63 did it, no more reboot and I can even OC the phone ! It works great no reboot, even with wavy usage of GPS navigation with CoPilot live over the week end ! this is perfect !
I only have an issue with the radio FM app which is buggy : sound start on the hp instead of head phone, favorite station are not kept, frequencies are written in green on black which is not visible and RDS name is overlapping frequencies ...
Another issue, I'm still not able to fine tune auto brightness to have good reactivity when phone get out of standb by on shiny day it take 1/ 1.5 second for the screen to detect it need to boost lightness ... Same when I'm in a call and I want to use the keyboard to dial, it takes 1/1.5 second for the phone to adjust brightness... I've tried several tutorial from forum but it still have this small lag in brightness reactivity.
Other the phone is now perfect to me in 2.3.5 ! Thanks very much slade87 ! One note I don't like the boot animation some less shiny would have been welcome ...
Cool you got it all working, yes there where instabilities with cross ROM/kernels.
I like the new bootanimation but you can allways change it out if you dont..
(update 7/7/11)[Boot Animation]more bootanim
Bootanimation Installer v3.3
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.
Hello guys, I've just installed the latest Hydrog3n-ICS ROM and Siyah v3.1 rc3 kernel and my LED touch keys stopped working. I mean, they do not light up when I click them as they once did. I know it's possible to turn them on permanently in device settings but I don't want this. I thought it could be because of BLN without wakelock setting in ExTweaks but then I turned it off and it's still not working properly. What can I do to fix this?
Installed another kernel and it's fine again.
I am running on foxhound sniper wolf rom with abyss 4 kernel and am very happy with this config, although I`ve been having some issues with the toggles from the pull down menu:
1/ First I noticed that the wifi, data and gps toggles weren`t working. This problem seems to be out of the way now, after having switched kernels (replaced built-in siyah by latest abyss 4, problem solved)
2/ But now I noticed that auto rotation, plane, brightness and timeout toggles aren`t working either (not sure if this was already the case before the abyss flash).
3/ Another thing that`s been annoying me is that when pulling down the menu from the lockscreen, the screen goes to sleep after a few seconds even when still sliding through the menu. So then I have to push the power or home button again to switch on the screen again. Frustrating.
Anyone else having similar issues? Any ideas on how to solve this? Thanks.
Reflash with a full wipe and if the problems persist change kernel after flashing the cleaning script..
Sent from my hybrid SII with the power of ParanoidAndroid and Fluxi kernel
thanks for your prompt reply.
So I ran the cleaning script to wipe cache, dalvik etc. Then I reflashed the abyss kernel, and the toggles now seem to work! Great, that covers part 2 of my original post.
Part 3 however still remains a problem.
Any ideas on that? Thanks!
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
It's probably a software issue, JB has tons of bugs. What kinda advise do you want? You need to re-install the rom (and clear cache ofc) and if that doesn't work re-install the stock rom via odin and then install neatrom if you want. And just don't use power save mode until you get an update? It's useless anyway... You can also try another kernel, this seems like a kernel problem.
Power saving actually just have a few advantages like turning of un-needed things like haptic feedback and some other stuff which you could do manually, and the main power saving feature is that it limits the CPU to use only 800Mhz max, this might be having some issues with Apollo kernel (as it works fine with stock or stock based kernel like Philz), but Apollo is a powerful kernel and will let you manually adjust the CPU limits even at your preferred limits manually, so if you want to save battery just manually adjust the settings instead of using Power Saving mode.
Sent from my GT-I9100 using Tapatalk
Perphide said:
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
Click to expand...
Click to collapse
It may be a bug in that rom. try another rom
Thank you!
Thank all of you for the help and advise!
I will no longer use the powersafe feature and start using the Apolo kernel again, since that kernel gave me the best battery life.
It might have been a coincidence of course that my S2 died/didn't want to start up no more shortly after using the powersafe feature... however from all of the above advise it seems that I don't need that feature anyway so I feel safe to switch back to the Apolo kernel again with my new installed NeatROM SuperLite 2.4.
If the problem returns I'll be here to post it, it might still be a bug in the Apolo kernel of the NeatROM ... I am not sure. Time will tell, or not if it had to do with the powersafe feature which I won't be using any more.
Thank you all!