I'm not sure it's because of franco #4 kernel, but I'm having a problem: the phone will freeze (the screen will stay intact from the previous state, touch screen and hard buttons don't work) when I run any app that turns to landscape (playing videos, games, or any normal apps that have landscape mode). Is it a known bug of this kernel, or any one have any suggestion? I'm using lewa rom with franco #4 kernel, but I recall having this problem when I used mik's 6.5.8 with franco v16 too.
Edit: Solved. Somehow disabling button savior helped. Don't know why though
Related
Im having random reboots/restarts after I start the camera application, it's happening to fast for a screenshot but what I do manage to see is something up on the top of the screen in white letters, RAMDUMP....Im not sure if all of this is happening b/c Im on a Franco Kernel and need to go back to Mik's Kernel for CM7, also in explanation, the problem shows a black screen which appears to be somewhat like BIOS screen's (something similiar) Is there a fix to this somewhere or is this a regular occurance and I should just stop using the camera ?
Jrhodes85 said:
Im having random reboots/restarts after I start the camera application, it's happening to fast for a screenshot but what I do manage to see is something up on the top of the screen in white letters, RAMDUMP....Im not sure if all of this is happening b/c Im on a Franco Kernel and need to go back to Mik's Kernel for CM7, also in explanation, the problem shows a black screen which appears to be somewhat like BIOS screen's (something similiar) Is there a fix to this somewhere or is this a regular occurance and I should just stop using the camera ?
Click to expand...
Click to collapse
Ive reflashed cm7, with the mik's default kernel-let's hope this does the trick, I really wanted to use Franco's Kernel v.18.1 bfs with performance/smartass but it seems like everytime I flash Franco's Kernal, I either get a random reboot or a kernel panic. Camera is now working but at the expense of just using Mik's kernel and not franco's ? Should I perhaps use an earlier version of Franco's Kernel or just stick with Mik's ?
Ive been using Glitch V12 (20110720-HL) for a while now with CM7. I stuck with this version because BLN (without app) and sensors work. I tried going to the newer releases but when using GrooveIP, I temporarily lose sound when the screen goes off while im in a call and doesnt come back until I turn the screen back on. Is this the screen state scaling? If so, any recommendations of what governor to use to that I wont get cut off but is also good on battery?
Thanks
If it is something that happens a lot, try either ondemand or disabling screenstate scaling completely.
Sent from my MIUI SCH-i500
Thanks for the quick response. Wasnt expecting to have an answer 'til I woke up. I will reflash back to the latest CM7 and Glitch tomorrow and report back.
Well, I flashed the latest Glitch kernel (9-23) along with CM7 (nightly 59) and its not doing it at all. When it did it before was on kernel 9-06. Did that build have a different default screen off governor or maybe it had something to do with the proximity sensors not working and the auto off screen kicking in after about 30 seconds, which is when the sound would stop before?
Sometimes when the phone wakes up, the screen is black and the buttons on the button are on. To get the screen to turn on, I press the top button and let the phone sleep for 5 secs, then I turn it on and it works.
any ideas why it's doing this?
Iccs? You must be talking about dax's rom. Its based on mik 6.5.8 which has the blackscreen bug.
ういこ!
InfiniteRisen said:
Iccs? You must be talking about dax's rom. Its based on mik 6.5.8 which has the blackscreen bug.
ういこ!
Click to expand...
Click to collapse
Yes, its dax's rom. I used mik's 6.5.8 rom without the black screen ever happening once.
ive been getting it too dude. good to get an asnwer instead of being laughed at lol.
Did you flash an updated kernel? If so that is why. Anything besides the old v18 kernel causes a blackscreen bug.
ういこ!
Flash the last goldenleaf or franco v19.4.
Update that should fix for you:
http://forum.xda-developers.com/showthread.php?p=16842877
ういこ!
I'll give it a try. I have been using the kernal that came with the rom.
Works
Thanks
Works
Thanks
My screen occasionally will not sleep. It does not even Dim.
I don't have any background apps installed like setcpu, oc etc.
Just straight apps. Calculator, weather bug (with backgroud updates turned off), etc.
It does not happen all the time. Just occassionally.
Sometimes even after a reboot it will just stay on and not sleep.
Some times just hitting the power button to force sleep fixes it. I wake it and then it goes to sleep fine.
I posted this problem in CleanROM thread and Scott (the CleanROM author) said he occasionally sees it to and does not know the cause.
I was curious if this occurred in other ROMs and if anyone might know the cause.
I'm running the Kernel that came with Clean ROM 2.9.5 by mwalt2 (with the DIM buttons and always on until cleared notification LED).
I also tried restoring CleanROM 2.5 and it did it too (I think it uses the same kernel).
Please use the Q&A Forum for questions Thanks
Moving to Q&A
mswlogo said:
My screen occasionally will not sleep. It does not even Dim.
I don't have any background apps installed like setcpu, oc etc.
Just straight apps. Calculator, weather bug (with backgroud updates turned off), etc.
It does not happen all the time. Just occassionally.
Sometimes even after a reboot it will just stay on and not sleep.
Some times just hitting the power button to force sleep fixes it. I wake it and then it goes to sleep fine.
I posted this problem in CleanROM thread and Scott (the CleanROM author) said he occasionally sees it to and does not know the cause.
I was curious if this occurred in other ROMs and if anyone might know the cause.
I'm running the Kernel that came with Clean ROM 2.9.5 by mwalt2 (with the DIM buttons and always on until cleared notification LED).
I also tried restoring CleanROM 2.5 and it did it too (I think it uses the same kernel).
Click to expand...
Click to collapse
Try reflashing the rom after doing a full wipe, and don't try to restore anything. I would also maybe try out a different kernel and see if that doesn't fix the issue.
#Winning# said:
Try reflashing the rom after doing a full wipe, and don't try to restore anything. I would also maybe try out a different kernel and see if that doesn't fix the issue.
Click to expand...
Click to collapse
I never restore anything after a wipe. Defeats the purpose of a "wipe"
I think it might be the Kernel.
People are to quick to say, I have no idea, so wipe it.
If I had to do that every time someone at work had a computer problem I'd be fired.
I have a question about the proximity sensor on the galaxy s2, mine is lit all of the time even when I press the power button to shut the screen off. Is this normal? I am running SHOStock 1.9.2 and Slyah 2.6.12 I have reflashed a couple of times and cleared the cache.
One more thing I think I found a possible bug in the flashlight toggle, if you rotate the screen with the flashlight on the toggle shuts off but the light stays on so you have to press the toggle twice to turn the light off.
Sent from my SAMSUNG-SGH-I777 using XDA App
I'm running SHOStock 1.9.2 and have neither of these problems. I even intentionally tried to get the flashlight toggle to break, but it work regardless of the orientation.
I'm not sure how long the sensor has been lit since it is so dim you can only see it in a dark room but I'm pretty sure it wasn't on the stock rom and maybe the first SHOStock rom I loaded which I believe was 1.9.0. The flashlight toggle issue has been there on all three SHOStock roms I have loaded.
Sent from my SAMSUNG-SGH-I777 using XDA App
I can't speak for the previous SHOStock versions as my first was v1.9.2.
I was coming from UCKH7 Stock (w/ Slyah 2.6.12 kernel). I did a full wipe and flashed v1.92.
I've only been running it for 3 days now, but overall i'm pleased. I did notice the following (not really issues, but a little annoying).
1. I had a random reboot within the first 24 hours of flashing.
2. I don't really care for the Auto Brightness changes (Lowered Auto Brightness a little and added 2 levels that make the changes less abrupt). I use Auto Brightness exclusively and it seems to low and a little choppy when changing.
3. I've gotten stuck in screen capture mode (home + power) twice. I know the screen capture is a feature, but I've got it to stick where I only need to press the power key (not the home + power combo). I'm not sure if this is a feature or a bug, or maybe I'm just a noob.
tikcolg said:
I can't speak for the previous SHOStock versions as my first was v1.9.2.
I was coming from UCKH7 Stock (w/ Slyah 2.6.12 kernel). I did a full wipe and flashed v1.92.
I've only been running it for 3 days now, but overall i'm pleased. I did notice the following (not really issues, but a little annoying).
1. I had a random reboot within the first 24 hours of flashing.
2. I don't really care for the Auto Brightness changes (Lowered Auto Brightness a little and added 2 levels that make the changes less abrupt). I use Auto Brightness exclusively and it seems to low and a little choppy when changing.
3. I've gotten stuck in screen capture mode (home + power) twice. I know the screen capture is a feature, but I've got it to stick where I only need to press the power key (not the home + power combo). I'm not sure if this is a feature or a bug, or maybe I'm just a noob.
Click to expand...
Click to collapse
You are not the only person having an issue with screen cap, tho I do believe it is due to the kernel you're running and not the Rom. A quick search should pull up a bunch of info for you
Sent from my SGH-I777
S2monkey,
Thanks for the tip. I'll do a search and see what I can dig up.
Sent from my SAMSUNG-SGH-I777 using XDA App
My phone stopped rotating so I flashed back to 1.9.1 (only version I had on my phone at the time). The orientation problem was fixed and I also noticed the proximity sesor was no longer lit. I flashed 1.9.2 and the sensor is lit again, reverted the kernel back to 2.6.11 with no change then flashed the 1.9.1 ROM and the sensor is still lit. I have no idea what caused it to go out the first time I reverted back to 1.9.1 or how to proceed. Does it really make any difference whether it is lit or not? I would think it would impact the battery life so any thought or ideas would be appreciated.
Sent from my SAMSUNG-SGH-I777 using XDA App