These are rare issues I have but I just thought I'd pose the question and see if anyone has any fixes. I have workarounds but still a nuissance and could be an indicator of a deeper problem (perhaps).
Back Button Looping
Sometimes when I hit the back button i begin looping and never get to the homescreen. It usually loops Go SMS --> Go SMS (again) --> Widget Locker in edit mode) then back to GoSMS. If i hit the home button then it brings me back to LauncherPro but does this mean the Launcher crashed? Why does it do this same sequence every time? (It has happened when leaving Plume, Camera, Titanium Backup...basically random apps, always does the same loop sequence when hitting the back button). Anyone else see this issue?
SOD
I had this issue on my TP2 and no one found a definitive solution. Random people experienced it no matter what, some saw it stop, some never saw it at all. Well it seems to have plagued my D3 in a much rarer form. After owning the phone for a few months it has only happened 3 times, and I have to battery pull for things to come back to normal. However the other day it happened while on a phone call...when i moved the phone from my ear the screen wouldnt come back on no matter what. I waited for the call lost tone and still the power button had no effect. Of course i still had the notification LED for an unread SMS which was more taunting me at this point, so again battery pull.
Everything I read dealt with Underclocking or Undervolting but I haven't installed any apps for this. Does LibertyROM or MonsterROM include any of that in their scripts? Are there any other causes out there?
Related
Hello XDA...
I've had my Xperia for about 5 months now...
First it started by being less responsive on certain letters on the qwerty keyboard and after that it started making double or even triple of the letter i pressed...
I have watched the tutorial on this site but i don't dare to open my phone
Although that is not my biggest problem right now... This problem is very persistent and QUITE annoying!
Let my try to explain it:
All hardware buttons are somehow assigned to different, RANDOM 'tasks'.
Pressing the right action button under the screen makes my phone go into 'settings', quickly overlapped by 'contacts' and then it marks the last inc/outg caller and calls that person.
My button to stop the call is assigned to Album.. so i can't do anything but to take out the battery....
When it starts freaking out and opening all sorts of programs and repeatedly overlaps everything by 'settings' i cant do anything...
I tap the cross in the corner to close everything and it just opens everything again...
I can use the touchscreen to type, text and call normally - but not the hardwarebuttons. Even the qwerty keyboard is acting wierd..
When i press the 'E' button, it is assigned to 'contacts' and 'settings' and 'new contact' somehow......
I have tried alot of different ROM's and the problem persists through all of them...
Has anyone EVER had this problem before?
Is there ANY solution at all?
I can upload a clip on youtube if anyone needs it visually explained.
Sorry for my english, it's not my native language.
No answers, hm? Seems like this is a unique problem.
For the record it is now fixed.
My phone wouldn't flash any SPL or whatever... I couldn't even force it into 'rainbow mode' by pressing volume-down and power..
I took out the memory card, and suddenly it was willing to go into rainbow mode...
Somehow i came to the conclusion that if removing 1 card fixed 1 of my problems, the second (SIM-card) would fix my other problem...
I took out the SIM-card and powered up the phone...
It was fully functional, with no hiccups or random apps popping up..
Tried putting my SIM-card back in, and now it's working again
So, no problems after that.
So far, my wierd fix is to:
Remove Mem and Sim card.
Start the phone.. - hopefully without any wierd stuff happening now.
Power off the phone.
Put back the Mem and Sim card.
- Wierd as it sounds, it has fixed my very annoying and wierd problem.
I am now a somewhat happy X1 owner again.
Right untill it started calling my girlfriend randomly and do everything it did before... ARGH, wtf?!?!
Hi!
I have a g1 and its freezing constantly. before one month it starts to freeze and I downgrade it to rc29 and root it and put cyanogen 4.1.999 and continue to update all cyanogen releases and it stops freezing. Now I am runing 4.2.4 and before two weeks the freezing thing get started again. first it starts to freeze when it get hot, when I use it for long time and it get hot in my hands. That was rerely happening first few days. Than it starts to freeze when charging and lately even when on standby. If it freezes when on standby the phone don't respond in any way only some times the volume buttons work and I can hear the sound of changing the volume when I press it, and even sometimes I can receive calls but the display don't work and no lights on buttons part. On the other hand when it freezes when I work on my phone it just freeze and there is no any respond from the phone. Buttons light are on and display is on. sometimes it get off, sometimes the display get off and buttons light is still working. Some times the freezing thing start in stages, firstly touchscreen and ball press won't respond. But I can move to another icon using ball and even enter it using the enter button on qwerty keyboard. And after some time even that part stop working and the phone is completly freezed. when I pull the battery out and return it back right after some times it wont turn on. And I just pull it off and leave it like that for half hour or more and it turn on normally. The only issue last few days it even starts to freeze while booting. I make a logcat and grabed the last_kmsg and its available in the attachment.
I hope someone is going to help me
ps. The phone is without warranty and there is no t-mobile or htc service center in my country.
Sounds like a hardware issue man, you may be SOL... You can try wiping everything, and re-flashing cyanogen 4.2.5, and see if that helps your issue.
Also, try underclocking your CPU, to help it not overheat as much, as that seems to be what your saying is causing the problem.
Leme know how that works out.
Try flashing a build that did not freeze for you, and stick on it for at least a week or two. If that build starts to freeze, it may be hardware.
I did wipe everything and put a fresh cyanogen rom 4.2.4. and it still occur.
How can I underclock my CPU?
btw. Thanks for help I hope its not serious hardware problem...
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
three threads above yours.
http://forum.xda-developers.com/showthread.php?t=681723
could be a hardware issue.
Mine does this every few days.. I am still on the stock 2.1 rom.
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
It happens to me as well, but very infrequently. Maybe every few days... so it doesn't bother me enough to worry about it.
I'm on stock ROM btw.
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Hmm, my problem's slightly different. Around half of the time, I have to press the power button twice to turn the screen on. Sometimes, pressing it the first time doesn't turn the screen on, had to press the power button firmly again.
This started only recently. On stock n1 and bought it during feb.
that means that your power button is dying, like many others' (including mine)
this is the first time, it takes 2 clicks to work....than it will increase.
Expect a repair soon...
Well i am having the issue other way around. i am not been able to put my phone in stand by mode by clicking on it and it is do a hard press then i get options to shut off the phone
any suggestions what might be causing it ?
I'm happy I haven't received this problem yet
-------------------------------------
i want my yogurt lol froyo time
negroplasty said:
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
Click to expand...
Click to collapse
I am having the same issue and i wonder if you were able to find the cause for it. I have the same rom as you do on your phone
negroplasty said:
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Click to expand...
Click to collapse
I have a similar problem. When I unplug the N1 from the charger, the screen comes on showing the lock screen, and I can't get it to turn off. If I unlock the phone, however, then the power button works normally. I don't think it was doing this until recently (I bought it in January the first day it was offered and am running the stock update1 ROM).
So here is my theory if the power button is a problem then it needs to act up both ways and not only one way. right now i can put the phone in sleep mode but i can wake it up. i will post the issues on the development forum and might be able to find an asnswer to it
So seems like the issues is because of Cyanogenmod 5.0.6 because since i have flashed another rom it is working just fine. i will be doing some more testing before i can be certain
Another problem I am experiencing is when I long press the power button, it pulls up the phone options menu but also turns off the screen. It's extremely frustrating as it does this quite frequently; right after I power on the screen again and unlock the device it works properly every time - so much so that I am convinced this is a software issue.
I am now running froyo, rooted with Cyan's minor root patch. I can also say for sure I experienced the same problem on CM 5.0.6, but it definitely occurred less frequently.
Am I alone here?
di2356 said:
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
Click to expand...
Click to collapse
I just started having this problem after upgrading to 2.2.
I have this every so often. But sometimes wonder if it is flyscreen doing it
You guys should all just be running the app no lock to take the power autumn out of the equation.
Ahhhhh! I just need trackball wakeup!
I have a similar issue where my screen will turn on but will be unresponsive. When i turn it on and off, the backlight jut comes and goes. If it times out it won't turn back on for a bit(the backlight will come on still).
I just wiped my phone, hoping that'll fix it since it only started happening on a regular basis since I updated to Froyo
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Svarto said:
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Click to expand...
Click to collapse
so the only way to escape this is by pulling the battery and rebooting? when you do reboot and dont go in standby, the touchscreen works fine?
You can check the issue using logcat and /proc/kmsg.
Also, you can read my threads on the subject, describing the same error with logs, and see if your logs are the same.
I'm currently trying to check if the error repeats itself after full wipe and starting from scratch. In the meantime it didn't show up until I applied a theme, and then after reflashing the ROM it's gone again - I'm still checking, only a day has passed.
Yes, the only solution is to pull out the battery and reboot. Then it works fine and I can go in and out of standby. I havent found a particular pattern to it happening so it is hard to reproduce.
I will have a look at that logcat and your other thread!
Just to guide you - when it happens to me, the phone gets stuck with mmc0 access that receives "CRC error" reply and doesn't go through. Pressing power button for a long time several times and playing with trackball / touching the screen between presses "releases" the "lock", and you'll be able to work with the phone again until you put it to sleep again. If you turn WiFi and BT off and then back on - the problem seems to disappear.
I have a weird issue that just started a few days back. I was on rooted 1.1 when the "Do you want to shut-down?" window would randomly pop up. If I did nothing, the unit would completely power off. If I hit the power button quick enough, the screen would shut off (putting it into standby) and the unit would not power off. I could then press the power button, swipe to unlock, and continue where I was.
I thought maybe it was related to me modifying the db to disable the auto-update from 1.1 to 1.2. However, I updated to 1.2 yesterday evening and rooted it as well. Unfortunately, the "Do you want to shutdown?" window started popping up again all by itself.
It's almost as though the unit thinks the power button is being pressed (and held). I tried squeezing the case around the edges, wiggling the power button, cleaning the screen, etc. There doesn't appear to be any particular reason why this is happening. I'm going to try wiping the device and flashing 1.2 again, unrooted, and see if the issue persists.
Does this sound like a hardware issue that requires replacement?
Restore your nook to stock and go to B&N and get your nook exchanged.
It definitely seems like a hardware fault.
I had the same problem with my first NC. I would be reading, doing whatever and the screen would blur and shutdown menu would appear. If I did nothing (and even if I hit cancel) it would shutdown as if the power button was just being held.
I had used the autonooter with 1.1 at the time, though I believe it was pure coincidence since the problem persisted after completely restoring to stock. My advice would also be to restore to stock and exchange it.
I consider myself lucky because I tried multiple times to restore to stock but would get interrupted since I had this problem even on boot. It was common for the device to interrupt boot so many times (>8 times) because the power button would get "stuck" that it would attempt to reflash. The button never felt physically stuck though.
I finally reverted to stock successfully, took it to B&N, showed a manager, during which the NC failed to boot, shutdown automatically, etc. and I had it exchanged no problem.
2nd NC works great though.
Thanks for the input - I will restore to stock tonight and take it in tonight or tomorrow.
I called one store - their "guru" isn't in until Tuesday.
I called another nearby store and the guy on the phone sounded irritated, brushed it off as a registration issue, and finally made it very plain that they will simply mail it off to the repair center if I bring it in...
After going back to stock 1.2 without root, the power-off message issue mysteriously disappeared. I've used it for 2 days now and have yet to see the message pop up.
Is it possible that it's software-related??