Hey I'm having an odd issue with my X10i. I received this phone second hand yesterday and went about rooting the phone. It was at 1.6FW then I updated to 2.1FW then to 2.3.3FW. Rooting process went perfectly well and the phone seems to be working great. However, the lock screen will end up completely blank with nothing on it! For example:
Phone is locked
Push pw button to get out of stand-by
LCD screen will get a little brighter but it is still completely blank; lower physical buttons will light up
After about 5-10 seconds, the screen will go completely out and the button lights will turn off.
This happened to me this morning when my alarm turned off. I got my phone as the alarm was going, push the stand-by button, same thing as above but the alarm sound will 'lag'. Once the screen and button lights turn off the alarm will go back to its normal beeping.
The phone is completely stock and with a locked bootloader. The tutorial I followed was:
http://forum.xda-developers.com/showthread.php?t=1196808
Here is some information in the 'About phone' screen
Model Number: X10i
Android version: 2.3.3
Baseband version: 2.1.71
Kernel version: 2.6.29-00054-g5f01537 ; [email protected] #1
Build number: 3.0.1.G.0.75
Can somebody help me out with this issue? Its annoying having to take the battery off and reinserting it every time this happens. I tried searching but really didn't find anything.
Anybody? This just happened right now. Again, its annoying to remove the battery every time this happens.
Be more patient, maybe cpu freq cant wake ur phone up.
Try it again and again, it sometimes happen to me when i opened an apps and then my screen accidentally locked, all i need to do just wait and try.
No problem mate.
Sent from my X10i using XDA App
id first try turning off auto brightness and reboot, if that didnt work id reflash via seus and root with flashtool.
Related
So it seems that no matter what i do regardless of rom, kernel, bootloader version if I press the power button while my gtablet is awake, it will just shut off- maybe twice now it has successfully unlocked for me and came back to life.
The other night i did a test, with 100% battery set the brightness to its lowest setting using the power manger widget (this seems to be 30 out of 255 btw)
Idling while I slept (screen on, sitting at the home screen) it ran 10 hours and still had 16% left.
Obviously the screen still remains as the key battery drainer, so my question is- is there a way to turn the screen off but keep the cpu running? Perhaps even just kill the back light completely- and upon volume button press or maybe a certain swipe gesture on the screen, the back light could be re enabled.
Ive tried a few apps, none of which have functionality quite like this- I was wondering about perhaps a script we could run via terminal (that maybe could be tied to a shortcut on the homescreen..?)
Thanks!
the sleep of death is my #1 gripe with the deivce.
what i am more interested in is why this happens. I would imagine this doesnt happen in stock form, so it must be an issue with rooting it.
Nope
No it happend in its stock form too... even with the 1.0 fw that i started with...
Went for the update to 1.1 bl and 1.2 bl
I really haven't been able to determine the issue and ive tried every rom between 1.1 and 1.2 ... (at least all the obvious ones on the forums here...)
Not sure what to do other than suck it up and just find something that can kill the screen.
Hello !
I recently bought a SE Xperia Neo which was running 2.3.4 without any problems.
I updated to 4.0.4 using SUS from my computer. After updating to 4.0.4 ICS I am experiencing the following issue-
Quite frequently (once or twice a day or so) the screen stops waking up. That is if screen is in sleep mode and if I press the Power/Wake Up/Lock-Unlock button, the screen does not come up. Only lights below Back-Home-Menu button at the bottom comes up.
In this condition, the phone is on, not like phone restarts or shuts down. If I call my number, phone starts ringing and vibrating but display doesn't come up.
The only way I need to follow is to pull up battery, reinsert and restart the phone. This is really being headache.
I have already done update once again using SUS (or reinstall) but the problem is there.
This problem wasn't there when I was using 2.3.4 for about a week.
Is anybody else experiencing the same problem ?
Any solutions please ?
Thank You
i experienced this when i updated my NeoV from 4.03 to 4.04. it seems to be a lock screen issue. this issue occurred when the lock screen was in slider mode. Now that i'm using pattern mode, the problem hasn't returned.
Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service
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
Hello, Everyone.
It's my first time posting here. I just received my phone yesterday with 64gb/3gb MTK variant. I have been testing it out and noticed that unlocking the phone is a bit buggy or is there a setting i can change? Here is the problem: When i unlock the phone via power button it turns on and after a split second the screen turns off. And if i try to unlock it again via power button it won't turn on. If i try to unlock it via fingerprint it turns on and everything is fine again. Is this a bug or a feature i can turn off?
Thank you.
jaydac12 said:
Hello, Everyone.
It's my first time posting here. I just received my phone yesterday with 64gb/3gb MTK variant. I have been testing it out and noticed that unlocking the phone is a bit buggy or is there a setting i can change? Here is the problem: When i unlock the phone via power button it turns on and after a split second the screen turns off. And if i try to unlock it again via power button it won't turn on. If i try to unlock it via fingerprint it turns on and everything is fine again. Is this a bug or a feature i can turn off?
Thank you.
Click to expand...
Click to collapse
Hi,
I don't believe that to be the default behavior when pressing the power button.
What is the version of your ROM?
Wilderone said:
Hi,
I don't believe that to be the default behavior when pressing the power button.
What is the version of your ROM?
Click to expand...
Click to collapse
MIUI Version: MIUI GLobal 8.0.4.0(MBFMIDG) Global
Baseband: MOLY.LR11.W1603.MD.MP.V13.18.P50
Kernel: 3.18.22+
Build: MRA58K
Additional: When I am playing a game the screen randomly turns off and the first mentioned problem occurs again. Or when i am just using the phone the screen turns off.
jaydac12 said:
Hello, Everyone.
It's my first time posting here. I just received my phone yesterday with 64gb/3gb MTK variant. I have been testing it out and noticed that unlocking the phone is a bit buggy or is there a setting i can change? Here is the problem: When i unlock the phone via power button it turns on and after a split second the screen turns off. And if i try to unlock it again via power button it won't turn on. If i try to unlock it via fingerprint it turns on and everything is fine again. Is this a bug or a feature i can turn off?
Thank you.
Click to expand...
Click to collapse
This happens after you leave the phone for a bit right? Not after you manually turn off the screen. I think what is happening is the moment you try to unlock it, the screen is not actually locked but the brightness is just way too low. This phone when left untouched has a two stage brightness dim
1. The brightness when you immediately stop using it
2. A lower brightness which comes 15 seconds after you stop using it and then it actually locks
The latest global developer ROM does not have this problem as they increased the second stage dim brightness so that users are not fooled into thinking that the screen has been locked