Is there any way to re-install the default lockscreen for un-rooted Desire?
The problem is, I installed Lock2.0, uninstalled it, now my Desire is really ****ed up. The locksceen goes off like after 1-2secs, so it need constantly touching to keep it awake. Theres not the "dim phase" at all, just black after a few secs. Reboot doesnt fix this.
Whats the weirdest thing, Keepscreen works only 50% of time so it doesnt solve the problem.
I had widget locker installed, it was working great since yesterday. Today this problem started.
Once the screen goes off/sleep, I can not turn it back on. Using either the home or power button. I removed widget locker, and set the home action back to ADW Launcher.
The phone is seemingly still working, because I was on a 10 min phone call, but after the screen would not come back on, so I couldn't end the call or use it at all. I have to pull the battery, and turn the phone on to use it, of course that's only useful until the screen goes off again lol.
Any ideas? I am going to wipe it/reapply the rom tonight to see if that fixes it, but not sure how it could be software now since the only new app lately was widget locker and I've uninstalled it. I also got rid of NoLed just in case it was that, although it wasn't enabled.
Thoughts? Suggestions?
I also noticed something while using Widgetlocker, sometimes when i unlock my screen, the "BACK" softkey when pressed does not vibrate the phone! the menu one does... I need to lock the screen and unlock again and voila... its working
Seems like Widgetlocker is bringing lots of problems
check what software you have installed recently
most likely one of those apps is keeping the screen off
AllGamer said:
check what software you have installed recently
most likely one of those apps is keeping the screen off
Click to expand...
Click to collapse
Well the ones I installed recently was Widget Locker. Before that I didn't have the problem, and I've removed that app. I haven't installed anything else in the past day.
I was just reading about setcpu potentially having this problem. Which would be weird since I've had that installed for a week and just now am having issues. I'm playing with it's settings now.
you can always to a quick format and restore the settings to ROM default
*2767*3855#
and reinstall each app, to see which one caused the problem
I cant seem to do a screenshot on lock screen. but the clock says 233 now and lock screen says 240. this happens all the time. ive tried turning off auto clock and network time. ive tried earing cache. my phone is rooted. but thats it. I am within period to return the phone. should I do that?
the only way I can find to fix it is turn off auto clock and then turn it on again. but it only fixes it and then it stops again anyways
help me quick please. if theres a solution I will do it. if not im returning this phone for good as this is my second problem phone.
s384 said:
I cant seem to do a screenshot on lock screen. but the clock says 233 now and lock screen says 240. this happens all the time. ive tried turning off auto clock and network time. ive tried earing cache. my phone is rooted. but thats it. I am within period to return the phone. should I do that?
the only way I can find to fix it is turn off auto clock and then turn it on again. but it only fixes it and then it stops again anyways
help me quick please. if theres a solution I will do it. if not im returning this phone for good as this is my second problem phone.
Click to expand...
Click to collapse
I have also unfroze all apps. restored my backup. restarted many times. stock rom. stock kernel. root is the only mod. I froze some apps while experimenting. reverted all back. problem persists. trying one more reboot after deleting system cache memory
seems to work after that reboot. but its going to happen again. im worried about missing alarms
What mods were made before restore? If 2 phones have the same problem it is likely not the phone.
I am using the D802, bought it in Singapore under M1. I also use the flipcover with the quick window - bug does not happen when i unlock using it. On stock with TWRP and root.
The problem first started when I rooted my device, I noticed that locking it and quickly unlocking it again would sometimes cause a soft reboot. The problem went away after a while, but today it has rebooted on me at least 8 times.
My logcat is attached below(no confidential stuff there). I seem to be able to reproduce the problem pretty easily today, so I started logging from when I turned on my screen and ends when the phone shows the lock screen when I finish the boot(when the lock screen appears)
Unlocking is attempted the moment the screen turns on and all the widgets have loaded(1second?), and the soft reboot occur both with double tap and using the power on key.
https://docs.google.com/file/d/0B3ooqFjmbeiFZDg3aHVUenFCWWc/edit?usp=sharing
I've already done a cache and dalvik cache wipe using TWRP 2.6.3.2 but it does nothing IMO
Any one has any ideas? I suspect a problem with me /system/bin/cnd file cos is keeps showing a "reading a NULL string not supported here" - it's the one error that keeps showing up. Any help would be really appreciated, thank you so much
I have seen this problem on many, many occasions with my T-Mobile G2 but in my case I did not dug that deep (logcat).
However I noticed the problem occurred while using either the Lockscreen Gmail Widget or the Launcher Gmail Widget.
Once I remove them, the problem is gone.
Cheers!
I see, thank you so much! Just removed it.
Rayan said:
I have seen this problem on many, many occasions with my T-Mobile G2 but in my case I did not dug that deep (logcat).
However I noticed the problem occurred while using either the Lockscreen Gmail Widget or the Launcher Gmail Widget.
Once I remove them, the problem is gone.
Cheers!
Click to expand...
Click to collapse
WOO. I thought I ****ed up my phone when flashing TWRP but you found it out Cheers. Going to submit bug report to gmail so they can take a look at this.
I don't wanna sound tacky, but saying thanks through the Thanks button is best!!!
Glad it helped!
Hi guys,
I flashed 5.0 over the weekend and the .33/84 hybrid modem to enable LTE. I also made Google Search my home launcher.
The issue is screen becomes black, just showing the status bar and navigation bar. The system bar and navigation buttons are responsive and i can access the notification drawer/system panel but tapping on them does not remove the black screen. The only way to fix it appears to be a reboot. It started out intermittently but now it's happening within just a few minutes of each reboot.
I've tried clearing cache partition from (stock) recovery but it doesn't seem to have helped.
Thanks in advance!
The pattern I've started to notice is that it happens when I get some sort of popup. For instance I use handcent for SMS and half the timeI get a text I end up getting the black screen. I just got a Facebook message and I'd imagine the little circle that shows up on the screen caused it this time.
I've gotten the black screen a couple of times over the last few days since installing 5.0 using the factory image. All that can be seen are the navigation and status bars and there is no touch screen response at all, only a reboot solves the issue. I never saw this happen at all before upgrading.
Have you tried using the .33/1.04 Hybrid modems? I have been using them since they released and never had this happen when using Messenger or Textra and getting pop-ups.
acejavelin said:
Have you tried using the .33/1.04 Hybrid modems? I have been using them since they released and never had this happen when using Messenger or Textra and getting pop-ups.
Click to expand...
Click to collapse
I haven't tried that modem. I've even returned back to the stock modem that came with the 5.0 image and am still having the same issue. Do you have a link to the .33/1.04 modem? Thanks
torchedlh said:
I haven't tried that modem. I've even returned back to the stock modem that came with the 5.0 image and am still having the same issue. Do you have a link to the .33/1.04 modem? Thanks
Click to expand...
Click to collapse
Honestly, if it does that with the stock modems, I would reflash the factory images clean, then use this one: http://forum.xda-developers.com/nexus-4/general/4-4-3-nexus-4-lte-lte-tethering-hotspot-t2416822
swallowingled said:
I've gotten the black screen a couple of times over the last few days since installing 5.0 using the factory image. All that can be seen are the navigation and status bars and there is no touch screen response at all, only a reboot solves the issue. I never saw this happen at all before upgrading.
Click to expand...
Click to collapse
Even i'm facing the same issue, have you found any way out?
acejavelin said:
Honestly, if it does that with the stock modems, I would reflash the factory images clean, then use this one: http://forum.xda-developers.com/nexus-4/general/4-4-3-nexus-4-lte-lte-tethering-hotspot-t2416822
Click to expand...
Click to collapse
Just reflashed 5.0 and seems to be going okay so far (haven't seen the issue). Is it okay to just flash the hybrid modem without using the rest of the LTE enabler? I don't mind having to manually select the network after every reboot...
torchedlh said:
Just reflashed 5.0 and seems to be going okay so far (haven't seen the issue). Is it okay to just flash the hybrid modem without using the rest of the LTE enabler? I don't mind having to manually select the network after every reboot...
Click to expand...
Click to collapse
Yes, you can certainly do that if you wish.
Crap. Still having this issue. Anyone else?
torchedlh said:
Crap. Still having this issue. Anyone else?
Click to expand...
Click to collapse
Yes, this is still happening and I'm just using the stock modem(not hybrid). I've also reflashed the factory image 3 times. I get the black screen at least once a day, sometimes only icons or folders or widgets disappear.
Im struggling with the same problem.
Stock 5.0 google image / With some other kernels / Even tried recent Rastapop. - Wiped System/cache/data, didnt help.
Also i have problem with connecting phones storage via USB. I can Barely access internal storage thru computer.
possible solution
Since I deactivated the app called "Tasker" my phone works just fine again... Plus that I deinstalled two other apps that required superuser rights.
Hope that helps others.
Still having this issue, even on 5.0.1 any ideas?
Okay I *think* I may have figured out the problem. I think it has to do with apps that try to enable/disable the lockscreen. I had Settings Profiles set to disable/enable my lockscreen based on location. I've just removed that setting and so far it looks like the problem may be gone.
I don't think this is a modem issue. If you Google "lollipop black screen" you'll get quite a few hits. I remember reading something last week about this bug affecting lollipop builds.
I'd say stick with the modem that makes you happy :good:
Stock modem and rooted on 5.0.1 and I have the same issue. In my case it is not random and only occurs specifically when I dial the phone from the Avast Mobile Security website (There is a test mode to call the phone). Not sure how they dial into the phone but the screen goes black with only the notification bar on top and navigation buttons on bottom. The notification bar works but the navigation buttons do nothing until the incoming phone call ends, at which time everything returns back to normal. Regular incoming phone calls do not exhibit this behavior. Now if I access the phone from the Avast website by entering a text message instead of a phone call, a pop-up appears on my phone along with my message, but it does not cause the screen to go black.
pete1450 said:
The pattern I've started to notice is that it happens when I get some sort of popup. For instance I use handcent for SMS and half the timeI get a text I end up getting the black screen. I just got a Facebook message and I'd imagine the little circle that shows up on the screen caused it this time.
Click to expand...
Click to collapse
Hum, sounds like it could be what I am experiencing...possibly a pop-up interfering with the phone call screen.
EDIT: (SOLVED). After contacting Avast via their forum, it turns out that they are doing this on purpose. It is supposed to prevent a thief from ending the call, although that is as simple as restarting the device.