I am having a really strange issue with my Blaze. I am not sure if it is a hardware problem due to a faulty USB or if it is from the Rom. I put a new jack in a month or so ago. I started using tthaz777 stock ICS 4.0.4 shortly after. A week ago the phone prompted me for an update, I declined it because I didnt want to loose my root. The next day I received another prompt, I accidentally confirmed so I did a battery pull. On reboot I got the expected message the update failed, but everything was working fine with 4.0.4. Next came a Simpsons update, I got the dreaded not enough space error (even though I had plenty). I read to clear the cache to solve this so I did and everything installed fine. About an hour after that my Home button went all screwy. When pressing home from inside an app (or while on a home screen to jump to the main home screen) instead of taking me home I jump to a different screen I have never seen before. It resembles a lock screen, except I don't need to swipe the screen to get by it. Hitting the back button or the X brings me back to the last app I was in. I figured it may have been something from either wiping the cache or stopping the update. I went to recovery and wiped cache and data and reinstalled 4.0.4. Seemed to work, for a few days. I did some app updates and out of the blue it started up again. I reinstalled after a complete wipe and it didn't solve the problem. I noticed sometimes it will do it while charging but go back to normal as soon as I unplug it which has me thinking I have a bad solder joint from the jack install and it is some type of charge screen, but I don't ever remember seeing it before and can't find a matching image on the net. I tried going back to 4.0.2 to see if I could duplicate it but the camera is buggy and it is painfully slow. I guess I'll have to try a KitKat versoin, which I despise to see if I can get it to happen again. Anyone had similar problems?
Related
[Q] HTC Desire "appears" as if it has the home button stuck, since a recent update
One of our HTC Desire is exhibiting very weird behaviour since a recent update (couple of days ago). It only affects one of the phone, the second one is working fine, both were updated within the same day.
** I will try to post the software version on the next post, I think it's triggering the "No outisde link for new user" error, even though there is no outside link!
This phone only started playing up about a day after the update, not immediately. It sometimes wake up on its own and bring up the "Recent Apps" screen, as if you have long-pressed the Home key. It then switches wildly between that screen and the zoom out (helicopter view?) view of all the home screens. Initially I thought it is hardware problem and the phone is 'screwed' but I think it's more software problem, since it can work normally sometimes.
The wild screen switching made it impossible to use the phone and because it is working constantly, it gets hot and drains the battery. The problem started to get worse when we plugged it into a PC to sync and it started to go crazy. Since the screen switching so wildly, I can't get into the menu to soft reset or turn off the phone properly. So had to hard reset it, and done that more than half a dozen times.
We did have an issue when we first downloaded that recent update, both phones didn't have enough space, so the install crashed out. We freed up more space and both phones appear to have installed the update fine. Well, until a day or so after, one of the phone started playing up.
At the end, I found that if I held down the optical cursor button (very hard work), it seems to hold off the wild screen switching. I can then sort of use the phone as per normal, so that I can join WiFi and change settings & install apps etc.
I noticed that the Rosie Utility is always showing on the "Recent apps" screen. I've never seen that on a normal "Recent Apps" screen before. Not knowing what it was, I googled and learnt that it's the SenseUI. I then compared the SenseUI info with AppKik and the crazy phone is showing a different size 1.9MB (laterly 2.0MB) whereas the working phone is showing 3.0MB, althought both said HTC Sense Version 1.0 com.htc.launcher.
So I figured something must have gone wrong with the SenseUI Launcher and hence it's doing crazy thing. So I downloaded couple of other launchers, LauncherPro and ADW Launcher. They initially seem to work then all of a sudden the crazy screen switching will start and they will get worse. It seems worst if I left it on the main home screen, if I was in an App, it sometimes stay calm for a while.
In frustration, I thought I will backup my SenseUI (rosie.apk) from the working phone using Appkik and then install it on the faulty phone, but the install failed. Probably because it's being used. Tried switch the default launcher to LauncherPro, still the same. May be it needed Root access to replace? So I rooted the phone with UnRevoke3 (after a long struggle getting the correct ADB working) but still can't install the rosie.apk.
Anyhow, after rooting the phone, it mysterously settled down. I could use the phone normally for quite a while, then it started again. Although not as crazy and only intermittently. Haven't used the phone later part of today, so not sure what it's doing at the moment. When I tried the phone this morning, I stumbled across an option to un-update the senseUI, so it's now supposedly switched back to the factory default (Eclair 2.1??) version? The info from Appkik is stil lthe same though.
My question to the experts are ...
1. Can I 'update' just the latest Rosie.APK since the phone update said I already got the latest and no more updates available. ? If so, where and how?
2. If not, can I download a working copy of Rosie.apk from somewhere, and how do I write that over the existing 'possibly' faulty version?
Any help will be greatly appreciated.
HTC Desire "appears" as if it has the home button stuck, since a recent update
Attached is the TXT file containing my HTC Desire Software Version details.
For some unknown reason, it won't accept my post if I had the text from this file in the body of the post. It keeps bringing up the error about no 'outside' link for new user.
Update: If I "Cleare Default" on SenseUI in the App2SD settings, then it appears to stop the Screen Switching, but the Home button stops working altogether, the rest of the home screens appear to work normally though. Very weird. I think the problem is definitely to do with corrupted Rosie.apk (com.htc.launcher) .
Hi,
In case it helps anyone else, my home and menu button on an hd desire became intermittently broken in that they would stop working for days.
I followed this and did a clear data on the rosie utility and they work fine now.
Whoop whoop!
It has started for about 2 weeks now. The phone pops up a message saying for me to save and that if I want to save before I turn off. If I try to turn off the screen, the top button wont react. I have to press twice to get it off, then it comes back on and it gives me the same message. I have to soft reset it to get it working again.
I also did a ROM update and that reset it everything, but then it started doing it again.
It is hardware right?
So this is becoming very annoying this ****e keeps popping up and its draining the ****e of my battery. Anyone has had this problem.
I don't really have a solution for this, but I had the same and also was thinking it's hardware related...
I tried opening up the phone and cleaning it out, first with no noticeable effect (except I broke my speaker wires, be carefull with that if you ever decide to open up your phone), but it seems like something went right, because I only rarely have that problem now ...
One theory I had was that water might have sipped in the button or something, so I'm leaving it out the bathroom when I'm taking showers now.
Anyway, if anyone else has had this problem and did something about it, I'm also very interested to know...
Actually to me, it sounds like some app has gone rogue. Have you installed or modded anything after you flashed the updated ROM? I would suggest if you have anything of importance, that you save/backup that information before performing a hard reset as this will reset everything back to stock for the ROM that you are using. I am using the ROM in my sig/signature and I am not experiencing any of the issues you are describing. It is a custom/cooked ROM so you will need to have HARD-SPL'd your device before you flash. Also, there is a CDMA version on PPCGeeks if you have that type of device.
n-Joie! (Enjoy)
So my Nexus S 4g been mighty stable, til this morning. i check my bank account on my phone then all the sudden, the back button starts blinking like crazy, and everything goes back if i open anything, and the vibrate feedback can be felt like rapid fire. So I hold the button so I can actually power off the phone into recovery.
Its still blinking, so I hold it down so it sends only one signal, so i can change my kernel back from Netarchy 1.3.7 to 1.3.6 where it still does it. Repeat to Mathkids. I also wiped the cache partition, and dalvik cache for this one. havent tried stock yet.
Anyone ever have this problem. Its still doing it. Thinking about going to stock and returning phone.
And if I do return it, do I have to unroot, and relock the bootloader?
tried stock kernel, did a few backups, formatted everything agian, turned back to stock and it hasnt stopped.
did notice tho if my hand or thumb got close to the back button, but didnt touch it, it would stop blinking. maybe it needs a heat sensative calibration? it wont stop flickering no matter what
It seems to be related to this issue: www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
Im having exactly the same problem, but with the searh button. In the Google thread a Google employee has replied, and according to him they're working on a fix (software related). This was posted a couple of weeks ago, i bet the fix is issued in 2.3.5, set to rls in the upcoming days.
For me the search button flickering seems to be related to how long the screen has been on, i.e. how warm it is. I can use it perfectly for 20-30min, but then its unusable for the next five. I discovered the relationship between screen on time and the flickering like a day ago and it may be incorrect. The Google employee says it is a software issue, but i dont hold my hopes high.
I was having this problem with the search button.
I goofed up something on the phone and ended up reflashing it back to stock like 5-6 times in the course of a night.
Ever since then, I havent had the issue pop up even once.
I also have read that it has to do with the NFC contacts on the battery cover. Someone was able to supposedly fix this by preventing the contacts from touching their corresponding contacts on the phone.
As of last night my tab 2 (p3100) has been playing up, have it running a pac rom, not updated in a while but all was working fine. Now when I do get it on, it lags a lot on home screen, can only really access anything for about 30 seconds before its practically unusable. When I try to power off or reboot it begins the process but ends up freezing, only way I can get it properly off it to plug it in to charge and then hold power for ages. Then getting it on again takes ages. Only thing I recall doing prior to these issues was installing the peel remote earlier that day, maybe just a coincidence but after that it all went wrong. I've just tried a factory reset and data wipe, seemed to initially solve the problem but after a few mins back to the same issues, any ideas?
edingal said:
As of last night my tab 2 (p3100) has been playing up, have it running a pac rom, not updated in a while but all was working fine. Now when I do get it on, it lags a lot on home screen, can only really access anything for about 30 seconds before its practically unusable. When I try to power off or reboot it begins the process but ends up freezing, only way I can get it properly off it to plug it in to charge and then hold power for ages. Then getting it on again takes ages. Only thing I recall doing prior to these issues was installing the peel remote earlier that day, maybe just a coincidence but after that it all went wrong. I've just tried a factory reset and data wipe, seemed to initially solve the problem but after a few mins back to the same issues, any ideas?
Click to expand...
Click to collapse
Try flashing another ROM, like CM 10.2 or one of the stock-based ROMs. Make sure to wipe data, system and cache before flashing. If the issue still persists, try restoring a backup that you know worked.
Will give that a go, thanks.
Hey,
yesterday i faced a problem i didn't knew of yet. As i mentioned sometimes, i came from an One M7 2 weeks ago as it didn't work the way it should - camera useless and awful battery life. I rooted the M7, had problems with it and so on - just how it is with a rooted phone + custom roms.
However, due to the DRM i didn't root my Z3 yet. Yesterday i took it out my pocket, thought it was a bit warm.. nevermind. It worked. 30 minutes later i pulled it out again, still warm, and screen wouldn't turn on. I reset it (power and vol+ for those who didn't know), tried to boot again.. well, it took several minutes and finally showed me the attached error message. The system performance was really, really low. Everything stuttered, i couldn't even enter my pin. A few forced reboots later i could finally enter my pin and get into my system only to notice that my data partition wasn't doing fine. I had to set language and so on in the initial setup process, apps kept force-closing in seconds. My own apps were still on the device, however when i tried to open WhatsApp there was no data there, i should have gone through the registration process. The phone froze after seconds each time. I tried to enter the fastboot menu (is it called that way?) while booting to just do a factory reset, didn't find the button combination. So finally, after i found home without navigation from no man's land (sure, why doesn't it happen at home anyway..), i managed to boot it, get through settings and initiate a factory reset. Of course, all the apps were deleted then and i could install all apps like LightFlow again. Had to re-enter all the settings i did in those kind of apps, it was kind of annoying.
So, my questions: Why the hell did this happen to my Z3? Not rooted, didn't even think of it. There wasn't a day on the One M7 without flashing anything and it never happened. It wouldn't have been as bad as it was on the Z3, as i HAD root, could have wiped data in TWRP in a matter of seconds and also had backups of my data, which i of course didn't have for my unrooted Z3.
Is it likely to happen again? Can any app do this on a non-rooted phone? I read a bit about the error, that it would be caused by some apps, but not in the extent as it happened on my phone. Most of the times it would just be an annoying error message.
I got a thing in always getting a defective unit, so i hope it isn't happening again on the Z3
Maybe the internal flash is corrupted/failing. I had a similar issue with my HTC One X I went to nap one day and half hour later it shut down, it restarted but boot looped. Eventually it showed no data partition as being mounted and completely died. They replaced the motherboard.
Better contact Sony, maybe you need a replacement.
Mh, actually that's the least thing i want to do.. I'd have to wait for at least 2 weeks to get it back and chances are that they won't do a thing or damage it (bad experiences with my former Razr i). It works just fine after the factory reset, no errors yet. If it should happen again, i'd of course send it in for repair but i think, until then i will use it normally, with more caution and backups of course.
Probably the cleanest solution HERE