when i press the power button and choose reboot option,my phone do reboot,but it would leave screen a blurring shadow and then reboot.anyone who use GingerBlur can test it.anyone know how to solve it??thx.
I believe this is known issue...it happens on my phone as well...
I think since the reboot option was ported over from another phone to the atrix, it is not fully compatible with our phone...the code would have to rewritten specifically for our phone...I could be wrong however, hopefully a more experienced dev can shed some light on this...
Happens with mine too, but seems just a cosmetic problem, as the reboot is fully functional.
Same for me, but never considered it an issue. Phone reboots fine.
Related
I am encountering strange touchscreen locks. They occured first with Google Navigation amd always after approx. 20-30 minutes of permanent display usage.
It looks like I would tap on the screen (I see the maginification buttons clicked in the lower right corner), but I cannot go back, because the screen does not react anymore. I have to use the power button twice to get it back to work, sometimes even that does not help. Imagine you want to stop the Navigation software (which is still talking) but you cannot...
This happens also with Navdroid, but the software seems not to be hindered as much as Googles Navigation. In any case, the screen does not react to touch anymore.
I also found this to happen after a longer telephone call, the screen does simply not react anymore, but still shows everything.
I had this effect with Megatron, Void, Prime, Miks CM7 and Andys Gingerbread ROMs, so is this then a hardware or a software (driver) issue? I cannot remember having that with the stock ROM, but that's a long time ago
With the Gingerbread ports there seems to be a problem with the screen after calls but am not too sure if thats the reason for ur problem as u had the same with Froyo.
I am on stock rom and i dont have any such problem. And i have never heard anyone else having the same problem. You could try wiping everything and then flashing a froyo rom again. If that doesn't work, it might be a hardware problem.
In case you do need to send it in to LG, you will have to revert it back to stock condition. When you do that, check if this happens then too.
Hello, I'm a new android and xda user. I tried searching for a topic like this but wasn't successful. I've had my atrix for 3 weeks now and I've been noticing that the touchscreen goes through bouts of unresponsiveness but if i have to change the orientation or turn the screen off and turn it on again or just type with my other hand (screen wont respond if i press key with my left hand but will if i use my right and vice versa) the screen will start working immediately but that doesn't usually last long and I'll have to rotate my phone around multiple times to type a text when i have this problem. Is this normal or do I have a defective phone? I noticed that on the latest update they did mention something about fixing problems that causes the touchscreen to be unresponsive but i have not noticed an improvement. I believe this is more prone to happen when the battery is at 30% but it could just be me having selective memory. lastly, it doesn't seem to matter how much i'm using the phone. could happen when nothing is running and i'm just trying to send a text.
I'm using a stock phone with whatever is the latest update for it with att and no screen protector. Thank you for any help!
Similar Issue
I used to have a similar issue, according to the Motorola site they fixed that issue in the latest update..... version 1.57 or something?????
Well either way the problem still persisted for me until i tried out the GreyBlur rom.... ever since i've updated to GreyBlur 2.1 and haven't seen the problem since.....
Points:
1) Motorola knows about the issue.
2) GreyBlur seems to solve it... (for me)
I'm currently running MiniCM7 Pro - V7 (paul-xxx) on my U20i. Before I get started, I will say a few things...
I am not running the V7x hotfix
I have not yet done a reinstall
I did do a factory reset full wipe before installing with CWM recovery
I also wiped the davlik cache prior to install
I previously was using Cyanogen Gingerbread CM7 based on MiniCM for MiniPro (v15.0) (slade87) (changed due to market issue)
The issue I have currently is that during charging the phone may become unresponsive (via usb or standard charging) The phone is still on (have received a call in this state), however none of the buttons can make the phone come out of sleep and bring up the lock screen. The only thing i have been able to do is pull the battery to reset the phone and be able to turn it back on. My current fix is to disable sleep during charging, and it has not had issues since. One time only it would not recognize the sd card but a reboot fixed that. I am curious if anyone else has experienced this issue before I do a full wipe then try to reinstall the rom. Other than this issue (which is probably my own fault) this rom is phenomenal, and I have had no other issues with it.
i've used the rom but never had an issue like the one you are describing.
just curious, are you using setcpu's screen off profile?
Everything so far is stock as the ROM comes, though I'm beginning to think it may be a hardware issue...
Another issue I have had is even on the stock ROM sometimes if I unplug the charger the charging indicator light stays on (and matches the color it should for charge level) and the icon at the top indicates it is still charging, and nothing but a reboot will make it go away.
Yes, if it happens with stock rom, it's a hardware problem...
Ok so I want to convey all the relevant information without this being a mile long.
I have a o2 UK SGS2 running on a 3 sim. I have flashed on Lite'ing 6.1 with ninphetmaine 2.0.5. Up until the following, everything has been 100%.
This morning I downloaded Destinia and played it for a while. Before quitting I took a quick look at in app purchases to see if they charge ridiculous prices (they do). I'm not interested so I quickly spam back to close everything. This is when **** ****s up. OS becomes unresponsive immediately and I have no choice but to pull the battery. (power menu disappears instantly, no registered actions from soft keys or menu button in OS). No change on reboot.
I try reflashing Lite'ning. Mostly no change but I got the chance to get into task manager and uninstall Destinia/Launcher Pro.
I reinstall launcher pro, and now it works most of the time except:
1. Quite frequently the voice action app will load itself, and the unlock notification will pop up.
2. MTP notification will appear occasionally and phone will act like it's plugged in
3. Random Launcher/OS crashes. Sometimes screen on but no response from apps or OS. Sometimes screen won't turn on at all, just softkeys and darkness.
4. at first unlock after boot, camera makes standard focusing sound.
5. on boot, little popup dialog will read "in app purchases not supported in this version of android".
Really I doubt there's going to be any solution other than "wipe and reflash" but I'm really interested if anyone knows what would cause all these problems.
Cheers
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
JJEgan said:
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
Click to expand...
Click to collapse
what this means is that pressed back from the game's in app purchases screen, back to the main menu and then back to the Launcher, I'm sure everyone has done basically this countless times.
Fine but my dictionary defines spam as a different meaning .
But as posted that's where it all went wrong for whatever reason .
jje
Right I wipe-flashed stock 2.3.5 and it's STILL doing this. Voice actions popping up at random, all sorts of apps crashing and hanging all the time.
This has to be a hardware problem now, right?
just a stab in the dark but run a virus check.
I've never had a virus in my life, but I checked anyway and nothing.
Right so I've been watching my phone today. It's still doing random voice action popups. If I leave the phone on standard standby it will be fine for a while. It will then randomly turn on the screen by itself. The screen will stay on, if i leave it long enough the whole thing become totally unresponsive. If I press power the phone will wait a few seconds, then restart. If I don't touch it, it will just restart on its own eventually.
Can anyone recommend at least, some logging software that will let me look at the underlying OS and see what's happening when this is going on.
Is there any possibility your phone also goes to car-mode by itself?
spare parts app??
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Im getting random voice talk and mtp etc. phone is all ovr the place. flashed litening and nimphet last week and seemed fine. used mhl hdmi cable and problems seemed to start from there.
millia90 said:
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Click to expand...
Click to collapse
Read your thread http://forum.xda-developers.com/showthread.php?t=1278790 and your problems are down to the letter the same. I've resigned myself to it being a hardware fault and put in a service request with samsung. Wish I had better news.
Yea me too. My issue is that my SGSII was manufactured in UK so I'm at odds seeing as how I'm in America. The people at the Samsung call center referred me to the UK number so I guess I will have to bits the bullet.
I'm currently having this issue and it's really frustrating, I had it first on the Galaxy S3 with 4.2.1 stock rom, I don't know if it might be an app that might be causing this, basically when i lock the phone the screen turns off but then when i press the power button or the home button to turn on the screen it does not do anything, I know the phone is still on because sometimes if i get a text message i can see the blue led blinking and it will continue to blink even when it's frozen.
The only way to bring it back is by holding the power and home button together in order to reset it.
I tried factory reset and it would not work, I flashed the phone with a custom rom for Paranoid Android 4.3 and it worked great for about a week, no issues at all, but then it started freezing when locked again. I hate this and i'm thinking it might be a hardware issue since I've tried different software versions.
I don't know if it might be an app that might be causing this, basically when i lock the phone the screen turns of but then when i press the power button or the home button to turn on the screen it does not do anything, I know the phone is still on because sometimes if i get a text message i can see the blue led blinking and it will continue to blink even when it's frozen.
Even worst, if i'm listening to music and i lock the phone or if the screen times out and locks when i try to unlock it i can see it's stuck but the music is still playing....
Also, if the phone is stuck and i try to call it, it will not ring not turn the screen on, it's not like the problem is just the physical buttons, i don't know what to do since the phone is out of warranty, I have never dropped the phone and there is no damage on it, it have never over heat either so i don't know what can i do.....
Any suggestions or help would be really appreciated.
hardware issue.I got same problem before but I didn't manage to fix it.
cz4r3n said:
hardware issue.I got same problem before but I didn't manage to fix it.
Click to expand...
Click to collapse
Thank you for the reply, do you know specifically what kind of hardware problem was it? Were you able to fix it or you just had it replaced?
no not yet sorry...
cz4r3n said:
no not yet sorry...
Click to expand...
Click to collapse
But it's really strange, It is a hardware issue and it should affect all the time, not randomly i would think... I don't know if the problem is with the processor or the buttons, i don't know how to determine that..
Jonhmena said:
But it's really strange, It is a hardware issue and it should affect all the time, not randomly i would think... I don't know if the problem is with the processor or the buttons, i don't know how to determine that..
Click to expand...
Click to collapse
The first week with Paranoid Android 4.3 it worked greatm even faster than the stock rom and I also liked it because it is android 4.3, the issue started one week after, and i'm thinking that during the first week i did not install all the apps i use, once i installed all the apps it started happening.
The first time i had the issue was right after the facebook messenger app was updated, i tried uninstalling it and the issue was still happening, if i check the running apps and i can see several of my apps running in the background such as Facebook messenger, Viber, Skype, Avast (6 services) Applock, GO weather EX, whatsapp, Facebook.
Maybe i'm just reluctant to think that this is a hardware issue, cause there is no way for me to get some logs or a hardware report that may show any crashes or anything.. I like this phone, it have everything i need and i refuse to think that it's a piece of crab but i've had nothing but troubles with it since day 1...
I dont think it is SW problem because even flashing multi package stock firmware doesn't fix the issue.I tried replacing lcd and display driver but still remain unsolved.
Edit:I think there is a defective sensor chip which I don't have a unit to test already.
hello, i have same issue, and stil stuck with it, anyone can help me?