Hey, I've just flashed CyanogenMod 10 Alpha 5. When I lock the screen, I see the TV effect, screen goes off and then blink for a half of second (turns on and goes off fast).
Does anyone has the same issue and is there any way to fix it?
Not a big problem, but it's a bit annoying.
It is normal with our phone
Sent from my GT-I9001 using xda app-developers app
Really? I didn't have this issue on the stock ROM and ivendor's CM9... Just wondering why this started right after I flashed CM10, if it isn't ROM issue...
I had same bug on SmoothieJB v2 ROM (also based on CM10 a5).
It stopped blinking when I set sleep (Settings - Display - Sleep) mode to "After 15 seconds of inactivity".
apkfox said:
I had same bug on SmoothieJB v2 ROM (also based on CM10 a5).
It stopped blinking when I set sleep (Settings - Display - Sleep) mode to "After 15 seconds of inactivity".
Click to expand...
Click to collapse
Worked, thanks
because of this "bug" i flashed another rom
but that´s a great solution
Problem still persists after I try this way
have you tried a different kernel?
maybe it is the kernel too
I think this only happens with Broodplank kernel
Sent from my GT-I9001 using Tapatalk 2
Related
Hi, I have an SGSplus (i9001) and I've been using arco68's and ivendor's CM9 ROMs for a few months now. Right now I'm using ivendor's latest RC9 plus CastagnaIT's ExtremeUV (without any OC, I'm using the standard 245-1401 MHz range) and it's fairly stable.
I always had some problems in real-time performance: it seems to me that when there is a process background the application in foreground becomes incredibly sluggish, maybe needing 10 seconds to input a single key… then, after a bit, the background process finishes his business and things go back to normal. Using BetterBatteryStats I have pinpointed a couple of bad application and removed them and now this happens rarely enough (but still happens). But this is not my question…
On Friday I decided to try ivendor's new CM10 alpha 5 and it simply doesn't boot: no "blue boy" loader at all.
I tried both the straight ROM and with the addition of CastagnaIT's kernel. I tried both with and without google apps (but I guess that doesn't matter at all, since that's userland stuff and I'm not seeing the kernel boot yet)
I put CM9 ivendor+CastagnaIT(extremeOC) back and everything is back to normal, but I'm wondering why CM10 is not booting; I think I've done it all correctly… using the new CWM 6.0.1.9 and all.
What could it be?
lap0 said:
Hi, I have an SGSplus (i9001) and I've been using arco68's and ivendor's ROMs for a few months now. Right now I'm using ivendor's latest RC9 plus CastagnaIT's ExtremeUV (without any OC, I'm using the standard 245-1401 MHz range) and it's fairly stable.
I always had some problems in real-time performance: it seems to me that when there is a process background the application in foreground becomes incredibly sluggish, maybe needing 10 seconds to input a single key… then, after a bit, the background process finishes his business and things go back to normal. Using BetterBatteryStats I have pinpointed a couple of bad application and removed them and now this happens rarely enough (but still happens). But this is not my question…
On Friday I decided to try ivendor's new CM10 alpha 5 and it simply doesn't boot: no "blue boy" loader at all.
I tried both the straight ROM and with the addition of CastagnaIT's kernel. I tried both with and without google apps (but I guess that doesn't matter at all, since that's userland stuff and I'm not seeing the kernel boot yet)
I put CM9 ivendor+CastagnaIT(extremeOC) back and everything is back to normal, but I'm wondering why CM10 is not booting; I think I've done it all correctly… using the new CWM 6.0.1.9 and all.
What could it be?
Click to expand...
Click to collapse
Dont call it blue boy his name is cid hm i flashed aokp jb in cwm 5 and all works fine try to flash cwm 5 via odin and try again because cwm 6 are buggy i think..
EDIT: first boot can take long time so be patient
Sent from my GT-I9001 using xda premium
Jonboy2011 said:
Dont call it blue boy his name is cid
Click to expand...
Click to collapse
Wops. :angel:
Jonboy2011 said:
try to flash cwm 5 via odin and try again because cwm 6 are buggy i think..
Click to expand...
Click to collapse
I tried with CWM 5.5.0.4 but it also doesn't work.
Doesn't hang on boot like it did with 6.0.1.9, but just resets back into CWM5 menu after a few seconds.
Oh, nice, it also resets back to CWM5 using the CM9 zip file which always worken with CWM6.0.1.2.
(I guess I'll use Odin to put CWM6 back and CM9 with that and be content with that)
lap0 said:
Wops. :angel:
I tried with CWM 5.5.0.4 but it also doesn't work.
Doesn't hang on boot like it did with 6.0.1.9, but just resets back into CWM5 menu after a few seconds.
Oh, nice, it also resets back to CWM5 using the CM9 zip file which always worken with CWM6.0.1.2.
(I guess I'll use Odin to put CWM6 back and CM9 with that and be content with that)
Click to expand...
Click to collapse
Hm have you try to flash aokp jb rom by crybert ? Full wipe flash full wipe and wait.. If this doesnt work your s plus is a transformer and at night a toaster sorry O-
EDIT : wait system.boots every time in.recovery without any butten pressed ?
Sent from my GT-I9001 using xda premium
Jonboy2011 said:
system.boots every time in.recovery without any butten pressed ?
Click to expand...
Click to collapse
Yep. That's what it did.
Now I've put CWM6.0.1.9 back with Odin and using that I managed to put ivendor CM9 RC5 back, so that I can put AOKP rom in the /sdcard and try it.
Whops. I guess that the changelog might explain what was happening.
2012-11-22: CM10 alpha4 [1] [2]
No changes only a working build, instead of the crappy alpha3 build
Click to expand...
Click to collapse
lap0 said:
Whops. I guess that the changelog might explain what was happening.
Click to expand...
Click to collapse
Whops oh sorry for the work with cwm :/
Sent from my GT-I9001 using xda premium
No problem.I wonder why CWM5504 didn't work for me, but oh well, newer ivendor CM10 RC5 just booted correctly, case solved!
Hello,
I have actually a samsung galaxy s i9000 device, running on CM 10.1
After a reboot, the screen turns pink.
Ive flashed and changed roms, formatted, cleaned partitions, did just about anything and it only works with stock rom and no with custom roms
I think there is no problem with the LCD at all
Thank you for your feedbacks / your help !
Can you give us a screenshot pls when display is pink than post it here again.
Sent from my GT-I9000 using xda premium
DerRomtester said:
Can you give us a screenshot pls when display is pink than post it here again.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
There doesn't seem any problem at all
What do you think?
flish3069 said:
Hello,
I have actually a samsung galaxy s i9000 device, running on CM 10.1
After a reboot, the screen turns pink.
Ive flashed and changed roms, formatted, cleaned partitions, did just about anything and it only works with stock rom and no with custom roms
I think there is no problem with the LCD at all
Thank you for your feedbacks / your help !
Click to expand...
Click to collapse
Settings > Advenced > Color tunning
Sent from my GT-I9000 using xda app-developers app
burakgon said:
Settings > Advenced > Color tunning
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
All default
flish3069 said:
All default
Click to expand...
Click to collapse
Did you try playing with the GPU rendering?
Settings - Developer options - Force GPU rendering (actually all options under Drawing can cause problems if they are not set properly.
Do you use any specific kernel or you always stay with stock one? Have you tried SlimBean ROM?
edit: after checking pics again, I see that you have glitches even in recovery :blink: I would say it could be a HW problem, broken cable or something like that. Flashing custom roms and the broking of cable at the same time can be a serious coincidence (or have you tried going back to stock 2.3.6?)
aToS88 said:
Did you try playing with the GPU rendering?
Settings - Developer options - Force GPU rendering (actually all options under Drawing can cause problems if they are not set properly.
Do you use any specific kernel or you always stay with stock one? Have you tried SlimBean ROM?
edit: after checking pics again, I see that you have glitches even in recovery :blink: I would say it could be a HW problem, broken cable or something like that. Flashing custom roms and the broking of cable at the same time can be a serious coincidence (or have you tried going back to stock 2.3.6?)
Click to expand...
Click to collapse
Stock 2.3.6 works fine so I think there is no problem with the LCD at all.
Cyanogenmod with ClockworkMod kernel turns the screen pink, but then I flash stock rom 2.3.6 with stock kernel and everything is fine.
I've tried flashing other roms like MIUI with Kernel Mackay CMC and it turns the screen pink as well.
Something in the custom kernels is not working on my device.
aToS88 said:
Have you tried SlimBean ROM?
Click to expand...
Click to collapse
I've just flashed SlimBean rom with Semaphore kernel and it turns the screen pink as well
Yes my galaxy s is same to you
I try many custom rom but after 2 or 3 days my lcd was yellow but not pink
What am i do??
Galaxy s i9000
Dude also the same problem with the pink screen plz anyone help we turned back to 2.3.5 but it too slow software.....
Plzzzzzzzzz anyone give us an explanation why this was happened????any solution.....
Hi,
my LG P880 power/lock key on the top is reacting very bad.
Sometimes I must press it 5 times to turn on/off the display.
The proximity senzor also not workinf very well, relatively often after call end the display doesn't turn on
and I couldn't hang up.
Have someone this problem?
Is any chance to solve these two problems without send it to warranty service?
For the proximity sensor problem you should calibrate it. Go into hidden menu (dial 3845#*880#) -> Device Test -> All Auto Test Menu - Full -> ALC / Proximity Test. There is an option to calibrate the proximity sensor.
And what about the lock screen ... Cos i somtimes press it 3 to five times before it displays
Sent from my LG-P880 using xda premium
jigga027 said:
And what about the lock screen ... Cos i somtimes press it 3 to five times before it displays
Sent from my LG-P880 using xda premium
Click to expand...
Click to collapse
Me too, is it hardware or software problem?
smoke2 said:
Me too, is it hardware or software problem?
Click to expand...
Click to collapse
Wich rom are you using??
if are cyanogenmod, you only have to change the kernel, relax it isn't a hardware broken it's only a bug in one of the kernel cods or some .lib.
if you are using a stock rom use kernel of eternity.
the problem it's the same in boths cases you only have to change kernel. pay attention in install the correct version of kernel for your rom.
The only way that i know to install a new kernel is cmw recovery and these are the kernel that i use.
http://forum.xda-developers.com/showthread.php?t=2256899 thats werewolf kernel
http://forum.xda-developers.com/showthread.php?t=2241474&highlight=eternityproject eternity
I recoment to us use a cyanogenmod rc 5 o estable version with android 4.2.2
magr281290 said:
Wich rom are you using??
if are cyanogenmod, you only have to change the kernel, relax it isn't a hardware broken it's only a bug in one of the kernel cods or some .lib.
if you are using a stock rom use kernel of eternity.
the problem it's the same in boths cases you only have to change kernel. pay attention in install the correct version of kernel for your rom.
The only way that i know to install a new kernel is cmw recovery and these are the kernel that i use.
http://forum.xda-developers.com/showthread.php?t=2256899 thats werewolf kernel
http://forum.xda-developers.com/showthread.php?t=2241474&highlight=eternityproject eternity
I recoment to us use a cyanogenmod rc 5 o estable version with android 4.2.2
Click to expand...
Click to collapse
I'm using stock rom v20a JB.
hi all, just a question to find others who are experiencing the same problem.
After updating (tried almost everything) to 4.2.2 i am having problems with my display. It is flickering. Especially in grey areas, but it is there on the the complete display. On every 4.2.2 rom this will appear eventually.
I've tried the stock rom, CM roms, FreeXperia roms, some others custom roms like RomAur 7.2, tried different kernels.
It's like the refresh rate is too low. like 30 or 40 fps. Or the refresh rate is not in sync with the screen updates. It is not there all the time and sometimes it is less visible. But it is there for sure.
Other people have the same issue??
exmatproton said:
hi all, just a question to find others who are experiencing the same problem.
After updating (tried almost everything) to 4.2.2 i am having problems with my display. It is flickering. Especially in grey areas, but it is there on the the complete display. On every 4.2.2 rom this will appear eventually.
I've tried the stock rom, CM roms, FreeXperia roms, some others custom roms like RomAur 7.2, tried different kernels.
It's like the refresh rate is too low. like 30 or 40 fps. Or the refresh rate is not in sync with the screen updates. It is not there all the time and sometimes it is less visible. But it is there for sure.
Other people have the same issue??
Click to expand...
Click to collapse
me too ....:crying:
I have the same. Noticed it today for the first time.
When I turn off the backlight is seems to stop, so I think it's more the lighting than the screen.
I hope it's a software issue and it gets fixed soon!
exmatproton said:
hi all, just a question to find others who are experiencing the same problem.
After updating (tried almost everything) to 4.2.2 i am having problems with my display. It is flickering. Especially in grey areas, but it is there on the the complete display. On every 4.2.2 rom this will appear eventually.
I've tried the stock rom, CM roms, FreeXperia roms, some others custom roms like RomAur 7.2, tried different kernels.
It's like the refresh rate is too low. like 30 or 40 fps. Or the refresh rate is not in sync with the screen updates. It is not there all the time and sometimes it is less visible. But it is there for sure.
Other people have the same issue??
Click to expand...
Click to collapse
it is software if u hadn't it on 4.1.2 so try to flash stock kernel and rom again
>> Wipe everything and then flash :good:
x102x96x said:
it is software if u hadn't it on 4.1.2 so try to flash stock kernel and rom again
>> Wipe everything and then flash :good:
Click to expand...
Click to collapse
+1 :good:
This is the first thing I noticed after installing 4.2.2. Currently I have a stock non-rooted rom.
I believe the problem is related to the background illumination, because when putting my finger onto the light-sensor, I can see how the screen darkens where the flicking is strongly visible. I looks like the illumination-level is not adjusted smoothly but rather coarse steps. Quite annoying...
x102x96x said:
it is software if u hadn't it on 4.1.2 so try to flash stock kernel and rom again
>> Wipe everything and then flash :good:
Click to expand...
Click to collapse
Thnx for this answer, ofcourse. I tried this several times. Now, i started completely from the beginning (ALL steps as written @ RomAur v7.2 rom) and the flickering was there again. I've changed some stuff inside dev options and it seems gone. Really don't know what i did. Disabled 2d gpu, enabled hw layer, disabled this again, enabled 2d gpu etc etc etc....it seems gone...really weird..i will keep this thread open for others and if something changes, i will write it here ofcourse!:good:
i have it when i use facebook i dont know if this was also on the leaked 4.2.2 but the official one has this issue meanwhile the battery issue. sony is sleeping maybe
Current settings dev options(flickering seems "as gone as possible):
-usb-debugging on
-verify apps over usb on
-show hardware layers updates on
-force gpu rendering on
-force 4x msaa on
the rest is off
i am using RomAur v7.2 with the DooMKernel v9
Performance control settings:
-max 1620 MHz (set on boot)
-min 192 MHz (set on boot)
-Gov interactive (set on boot)
-IO deadline (set on boot)
-sd read ahead 256 kb (set on boot)
-vm settings (set on boot)
maybe this will help other people as well?? please, let me know
exmatproton said:
Current settings dev options(flickering seems "as gone as possible):
-usb-debugging on
-verify apps over usb on
-show hardware layers updates on
-force gpu rendering on
-force 4x msaa on
the rest is off
i am using RomAur v7.2 with the DooMKernel v9
Performance control settings:
-max 1620 MHz (set on boot)
-min 192 MHz (set on boot)
-Gov interactive (set on boot)
-IO deadline (set on boot)
-sd read ahead 256 kb (set on boot)
-vm settings (set on boot)
maybe this will help other people as well?? please, let me know
Click to expand...
Click to collapse
Never mind this...still flickering.
Sent from my C6603 using xda premium
I just got it flickering too. For now it only happened in the movies app or when playing a video from Facebook for example. Only the lower side of te screen flickers. Also, when pushing on the screen the flickering stops for a while!
Sent from my C6603 using xda app-developers app
sandrin0 said:
I just got it flickering too. For now it only happened in the movies app or when playing a video from Facebook for example. Only the lower side of te screen flickers. Also, when pushing on the screen the flickering stops for a while!
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Any workarounds for this? I'm facing the same problem too. It's annoying.
I had the same issue a few days ago and it has seemed to go away after what I did, not saying it will not come back.
1.) Made a nandroid backup of my system, using ExistenZ v4 rom as my rom
2.) Flashed my country specific FTF, using flashtool, rom downloaded from Sony Update Service. I went all the way back to .434
3.) Rooted and then added recovery to my stock rom
4.) Flashed the .423 kernel only in flashtool
5.) Booted into CWM and restored my backup of my original rom
6.) Booted back into rom to make sure everything came back
7.) Flashed baseband from my country specific FTF
I have not seen any flickering for about 2-3 days now. Hoping it will stay way this time.
DarkStone82 said:
I had the same issue a few days ago and it has seemed to go away after what I did, not saying it will not come back.
1.) Made a nandroid backup of my system, using ExistenZ v4 rom as my rom
2.) Flashed my country specific FTF, using flashtool, rom downloaded from Sony Update Service. I went all the way back to .434
3.) Rooted and then added recovery to my stock rom
4.) Flashed the .423 kernel only in flashtool
5.) Booted into CWM and restored my backup of my original rom
6.) Booted back into rom to make sure everything came back
7.) Flashed baseband from my country specific FTF
I have not seen any flickering for about 2-3 days now. Hoping it will stay way this time.
Click to expand...
Click to collapse
I tried a similar (well, at least the cwm back-up and restore) re-install this morning. The whole day no flickering. Will keep you posted ofcourse.
Sent from my C6603 using xda premium
exmatproton said:
I tried a similar (well, at least the cwm back-up and restore) re-install this morning. The whole day no flickering. Will keep you posted ofcourse.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Okay, getting pretty mad about this...flickering is back again...
Sent from my C6603 using xda premium
turned security off
Turning security off (was using facial recognition) made my screen flickering go away. 2 days and counting. YMMV
AFinch said:
Turning security off (was using facial recognition) made my screen flickering go away. 2 days and counting. YMMV
Click to expand...
Click to collapse
Lol. Trying that right now. Still no flickering...wtf??
Sent from my C6603 using xda premium
AFinch said:
Turning security off (was using facial recognition) made my screen flickering go away. 2 days and counting. YMMV
Click to expand...
Click to collapse
Hhmmm, still no flickering display over here. Using widget locker instead...all good for now
Going to let it setle for now and gonna change the settings in a couple of days to see if it will start flickering again...
Sent from my C6603 using xda premium
exmatproton said:
Hhmmm, still no flickering display over here. Using widget locker instead...all good for now
Going to let it setle for now and gonna change the settings in a couple of days to see if it will start flickering again...
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Yet another day without filckering.....security settings off. What kind of bug is this??
Sent from my C6603 using xda premium
I have a same problem sometime. In stock AOSP browser and Aqua mail.
Hi,
I flashed with CWM the stable Slimkat (Slim-galaxysmtd-4.4.2.build.3-OFFICIAL-3067) and I have to major problems:
- keyboard is not showing up. When it is supposed to pop-up. It doesn't.
- the 'back" button is not working at all. when I press it, the phone vibrates (it got the signal) but it doesn't proccess it.
I didn't have these problems with Slim-galaxysmtd-4.4.2.build.2.8.RC3-WEEKLY-2884.
Any ideas?
Thanx,
Sp
papage said:
Hi,
I flashed with CWM the stable Slimkat (Slim-galaxysmtd-4.4.2.build.3-OFFICIAL-3067) and I have to major problems:
- keyboard is not showing up. When it is supposed to pop-up. It doesn't.
- the 'back" button is not working at all. when I press it, the phone vibrates (it got the signal) but it doesn't proccess it.
I didn't have these problems with Slim-galaxysmtd-4.4.2.build.2.8.RC3-WEEKLY-2884.
Any ideas?
Thanx,
Sp
Click to expand...
Click to collapse
the same problem happened to me for the second time in 2 months, this is mind boggling, Nexus 10 stock 4.4.2
keyboard (stock and all other keyboards) stop working + back button also stops working out of the fkin blue..
I can't for the life of me understand what could cause this.. so f***in frustrating.. only a hard reset fixes this BS.
anyone has any info on this ?
This is due to flashing other gapps rather than the gapps provided by slimbean team. You just need to reflash the ROM with their gapps pack.
Sent from my GT-I9000 using xda app-developers app
leecorp said:
This is due to flashing other gapps rather than the gapps provided by slimbean team. You just need to reflash the ROM with their gapps pack.
Click to expand...
Click to collapse
:good: