Hello,
I flashed cm-10-20131006-NIGHTLY-smultron.zip today. I used the boot.img file from it and flashed it separately with the flashtool and
then I installed the zip from SD card with CWM.
The Problem I have is:
When I turn the phone on there appears the last screen before the phone was switched off . This happens very short for approx 0.1 seconds(it doesn't affect if I just removed the battery or shut-down properly before the new boot) and only then It comes the picture of the kernel as should do. -It looks like a untidy framebuffer
WHY is this "last seen screen" always appearing at the begin? (known bug or defective phone?)
-Appart from that the phone works correctly.
greets
Janez
OCD much? haha, you're just looking at whatever your LCD panel was displaying before shutting off. It happens on all phones.
You see, if you could keep the backlight on when you pull the battery out, you'd see the LCD doesn't go blank instantly.
Related
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
Hi, so sorry for the vague thread title, but really, there's no other way to describe it. So here's what happened.
For the past few weeks (or month), my Xperia Ray has had a problem of switching on after it was put into standby mode, i.e. after i pressed the lock button. The screen would light up, however would remain blank. So all I would get is a bright black screen.
I could have lived with this for a few more months (until Xperia Z gets released in my country D: ) however this problem started getting worse. At first, after pressing the home button, the volume rockers and/or the lock button for about 20 times, the screen would turn on (finally). Despite it giving me that bright black screen, i could still operate the screen. I could still try to unlock it because of the haptic feedback on my lockscreen. I could still change music tracks on my music widget on my lockscreen. In short, the screen worked perfectly, only that it kinda wouldn't show. However, for the past week, the only way to turn it back on would be to do a battery pull and switch on the phone again. And it recently developed a problem of giving me that bright black screen again when I switch it on, causing me to do about 5 battery pulls before being able to actually use my phone again.
I did get fed up with this problem, being a heavy user of my phone. Therefore, today I decided to try to do a factory reset of my phone, intending to wipe the dalvik cache + clear all user data, thinking it might help my bright black screen problem. However, I found that I couldn't boot into recovery because all my phone would do was to give me that bright black screen again! So after many battery pulls, I managed to boot up my phone normally and do a factory reset under the backup & restore tab in settings. Of course, the phone tried to reboot itself, but of course, just gave me the bright black screen.
I kinda gave up at this point, and did many battery pulls and boots, however, all I got was either
1. the terrible bright black screen
or less frequently
2. the free xperia project logo then the terrible bright black screen.
I did get very fed up, so I plugged it into a wall socket to charge it. However, since about an hour or two ago, I realised it may be on bootloop. When I plug it into a wall socket, the free xperia project logo shows up and then an even brighter black screen shows up for about 3-5 minutes, then those two repeat endlessly. The notification light doesn't show that it's charging at all.
Okay here's background info on my phone.
- Is rooted
- Bootloader is unlocked
- CM 9.1 is installed
- Was running GO Launcher (if that helps)
- had a custom boot animation
- I think i deleted an apk for the google start up configuration thing...the one that asks if you have any google accounts you want to connect when you switch on your phone for the first time. I'll search up the correct apk name if you need it.
- Is about a year old (got it last early April)
- is a Sony Ericsson Xperia Ray (in case you didn't notice haha)
- battery level was about 20%+ when I did a factory reset (terrible of me I know)
- I have tried to caliberate the battery a few months ago
That's all the background info I can think you need. Please do let me know if you need any other info. If you need the logcat text of what happens when I hit the lock button at the top of my phone and the phone gives me the bright black screen (the early stages of this problem), let me know and I'll dig it up. I think I've bricked it, but I can't boot it into recovery so I can't do anything. And I did all I could google for the bright black screen problem which I won't tire you by specifying here. Please do help me. It seems as if the worst of evils has befallen my phone. Now I'm stuck here with my phone crazily on bootloop beside me. Please please do help.
Flash stock rom
Just try flashing a stock rom with Flashtool. If the problem persists, then it could be a hardware problem. Flashing a stock ftf takes care of all software issues. Get the stock ics FTF file and place it in firmwares folder of flashtool. Start flashtool and select flash mode. Then choose your ftf and press ok. Then wait until it prompts you to connect your phone. Then, just turn off your phone, while holding the power button down attach the USB cable. The LED notification should turn green and wait until it finishes flashing.
flash extended stock kernel and then the stock ftf firmware file...
hit thanks if i helped u
I have the same problem on my Xperia Mini (ST15i) I use Pureness rom and Mesa Kernel... ((
Benlux1 said:
I have the same problem on my Xperia Mini (ST15i) I use Pureness rom and Mesa Kernel... ((
Click to expand...
Click to collapse
Hi, if your phone can still be switched on and hasn't progressed so far in being destroyed, you could try downloading the Disable Auto Brightness app for Xperia phones from the Play Store. I've read somewhere that the screen might not turn on because of the auto brightness. I'm not sure if it actually helps, but perhaps my phone would have died faster without it. I've read of people changing their battery, doing battery calibrations or changing their screen to fix the problem. But before you change the hardware, I suggest that you check the hardware first. If the Disable Auto Brightness doesn't work, do a Nandroid backup and store the backup somewhere safe. Then flash the stock firmware to your phone and try to get it to switch on. Do flash the firmware before your phone runs out of battery because you never know, your phone may decide to refuse to charge your battery anytime. Then try to switch it on. If your phone goes into a bootloop (like mine now) really consider getting a new phone or sending it for repair or try all day to fix it if you use your phone alot. I'm still trying to fix mine.
I flashed the original firmware for my phone, tried to turn it on, was very happy when I saw the original Xperia logo, but then I realised it was on bootloop. When I tried to charge it, it immediately turns on and goes into bootloop again. Logcat doesn't detect my phone, so I can't obtain the logcat of what's happening. I haven't tried to replace the battery of my phone because I couldn't find a supplier. But I'll go on trying to fix my phone until the day that it really breaks down. Good luck with yours and keep us posted.
Sent from my MT25i using xda app-developers app
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
(I posted on the wrong location first time, sorry)
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
Hi, I have an xperia sola with ultimate rom v10 and experimental kernel v7. I just noticed this issue so I don't know if it's related to them or not.
I don't know quite how to describe it but I'll try. When my phone is booting (the sony logo) and when I'm in CWM, I see the ghost image of my phone's homescreen on top right and left. It's a silhouette of the time, the battery percentage and the notification icon. The image always changes to the last state when I experience it (for ex. if the time was 17.12 before I shut down, the silhouette says 17.12 too).
There is no ghost image whatsoever after the device boots though. I've carefully checked it only occurs when booting and when in CWM. Is this an issue or I'm just making a fuss over nothing?
Hi dnilbia,
I noticed your problem on my Sola with stock not rooted 2.3.7 GB! I can see the time and avast antivirus logo on the right and leftt top off the screen (where notification bar is),when my phone is booting or is charging powered off!Moreover on the left and right bottom of the screen there is a blurry small black "triagnle" (the edges of the screen).
Well seems like a problem of old lcd screens with lcd persistence image but maybe it is caused from moisture and low temperatures!Well mine disappeared some days ago,boot per boot it was disappearing a little bit til it was gone.I left it in dry environment and avoided using YT cause screen is always on!
Hope it is nothing