Develop Bugs

[Q] SD Card causing Power Button to be Unresponsive?

So about a week ago or so I began, out of the blue, to have power button issues. The power button would turn my incredible on when it was off. It would wake it when it was asleep/screen off. After that it became hit and miss. When the screen was on it was highly unresponsive. Sometimes it took several presses to get it to turn off, sometimes I couldn't turn it off at all. Sometimes a tap would bring up the shut-down menu as if I had long-held it. Long holding it usually didn't work either. A few times I had to do a battery pull just to shut it off. I eventually downloaded quickboot and a screen lock widget just to get that functionality back. The last thing I remember downloading before this started happening was 'reddit is fun'. I uninstalled that after the problems, but to no avail.
Now lets go over what I was set up with. I have an amoled unit. I was at the time using CM7 Final and whatever kernel was included with it. Although I have used it a lot in the past, I didn't have setCPU installed or running this time. The only root-required thing I can remember running was autostarts. No changes were made to autostarts in the weeks leading up to the problem. I have used many roms; Frankenrom, Virtuous, Ruby, ShadowRom, IncDoes AOSP, The New Guy, Warm 2.2, Redemptive, SkyRaider, Evervolv, and several of the CM Nightlies. While using Redemptive my radio completely quit working across the board. Returning it to stock and then re-rooting fixed it. As far as I can remember I had only used SkyRaider, Evervolv, and the CM Nightlies up until I was using CM7 Final.
So after the problem started happening I decided easiest thing to do would be to try and flash a nightly over it. Tried that, didn't work. That was kind of a long shot, and I decided I might need a full wipe. Did the full wipe and installed the latest nightly. The problem persisted. I think I flashed the latest SkyRaider then, still had the problem. This was starting to seem kind of serious so I did another complete return to stock. I booted into the stock rom and used it for a bit, maybe a few hours, it seemed to work. Since things seemed back to normal I flashed the latest CM Nightly again. Seemed to work for a minute, then it was back to the same old problem.
Now around this point I, for reasons I can't remember, remove my 16 GB SD card and put the stock 2 GB one back in. I have SkyRaider on that and I flash it, it works perfectly. In fact it continues to work for a day or two. All this time my old 16 GB is sitting out on my desk. I eventually decide to clean it up, deleting a bunch of stuff I didn't need on there, and throwing it back in. After putting the 16 back in the problems creep back in. Here and there, then only working half of the time, then barely working at all.
About this time I come up with the idea that maybe something on the SD card, or the card itself, is causing this problem. Seems like a long shot, but I can't think of any other reason that would fit. I do not install apps to my SD card.
So I pull the SD card out. I was at work and I didn't have my old 2GB, so I just left the slot empty. It seemed to still be messed up, but over the course of the next hour or so it began to work correctly again.
Now I'm at home and I have deleted everything from my 16GB, and reformatted it completely. I'm about to flip it back in and see how things go.
The strange thing about this whole situation was that the problem didn't seem to just start and stop. It was as if it phased in and phased out over time, but always being caused by certain things. It seems organic if you know what I mean by that.
Feel free to tell me this is a really ridiculous idea. I think it might be. Is there something critical to the android system that could possibly be stored on the SD card?

Maybe its a hardware problem that's being affected by the weather in your area, because you can run android fine without an SD card. You would be surprised how the humidity affects electronics. This is just a crazy thought to a crazy problem lol

Wow, finally there is someone else out there with this problem.
Mine didnt have this problem till i flashed MIUI latest rom....but even after somehow making it into the recovery mode...i was able to restore my previous cm7 build...
BUT....the problem persists....
So I think I am going to pull out the 8gb sd card my friend gave me from his EVO 4g.
It annoying because sometimes i cant get into even hboot with power + volume down.
I know the volume buttons work because i can change volume on phone.
I can still see the power button still being pressed down, its not stuck or anything...it works 50/50
Can you give an update OP, please?
I also have an AMOLED Incredible..and dont want/can afford another phone...

have any of you opened up your phone to see if the button was still soldered to the board?
- i did and it is, same issue.

[Q] Phone freezing for no obvious reason, looking for advice.

I really have no idea what is going on with the phone. The phone is amazingly fast and snappy normally. I'm running [ERA]EPICUREANv7 EGgs22, with EC05 modem (I believe I read that staying on EC05 would be fine, correct me if I'm wrong).
It started happening once I transferred my old files from my old SD card to my new SD card (this is my second epic, first one died without any explanation). It began freezing within a minute of a reboot. I then took the SD card out, and it was fine again. I deleted all my old music and pictures for a clean SD, and the problem went away.
The next day it froze again, and the day after that (today), it froze again just now. It seems to happen when I am running a new program (happened once when i installed and tried out miren, happened once when I opened google music for the first time, happened once with powerAMP, etc) but I'm not sure if that is the cause. I'm starting to wonder if there is a common factor between these freezings and how my old epic became a brick (not really a brick, I odined it through download mode to stock, but flashing any rom now causes it to be unable to boot as far as I've tried so it's perma stock now)
Does anyone know what is going on? Is there any kind of diagnostic app out there that will tell me what is causing the freezes or high usage?
Thanks in advance!

[Q] GSM Galaxy Nexus force close & reboot ****storm

I have searched for this issue but couldn't find anything about it...
So I got my GSM Galaxy Nexus from Rogers 10 days ago. It has been working dandy with maybe 1 force close the whole time and no random reboots. I also unlocked the bootloader and installed 4.0.2 (yakju) keeping the radio that came with it intact.
I also installed Google Wallet on it and successfully used it. Other than that, I haven't done any tweaks, and like I said, it has been working perfectly with no problems whatsoever.
Enter today: I woke up this morning and went to check my phone. Instantly like 3 applications force closed (ones that weren't even running in the foreground too). Now for the past 3 hours hours or so, applications force close (some won't even have a chance to run for a second) and the phone reboots randomly. I think it has rebooted around 30 times in the past 3 hours. Sometimes it reboots as soon as it has booted up, sometimes it works for a few minutes before rebooting.
Every time it reboots it shows my old battery stats (I think.. from before I went to sleep), and notifies me of the same emails. I managed to install one app before it did a random reboot once, but after the reboot it was gone. (Think Groundhog Day).
I have no idea how to fix this short of doing a factory reset. Anyone have any ideas as to what may be happening or how to fix it?
Thanks.

stenzor said:
I have searched for this issue but couldn't find anything about it...
So I got my GSM Galaxy Nexus from Rogers 10 days ago. It has been working dandy with maybe 1 force close the whole time and no random reboots. I also unlocked the bootloader and installed 4.0.2 (yakju) keeping the radio that came with it intact.
I also installed Google Wallet on it and successfully used it. Other than that, I haven't done any tweaks, and like I said, it has been working perfectly with no problems whatsoever.
Enter today: I woke up this morning and went to check my phone. Instantly like 3 applications force closed (ones that weren't even running in the foreground too). Now for the past 3 hours hours or so, applications force close (some won't even have a chance to run for a second) and the phone reboots randomly. I think it has rebooted around 30 times in the past 3 hours. Sometimes it reboots as soon as it has booted up, sometimes it works for a few minutes before rebooting.
Every time it reboots it shows my old battery stats (I think.. from before I went to sleep), and notifies me of the same emails. I managed to install one app before it did a random reboot once, but after the reboot it was gone. (Think Groundhog Day).
I have no idea how to fix this short of doing a factory reset. Anyone have any ideas as to what may be happening or how to fix it?
Thanks.
Click to expand...
Click to collapse
Is it doing a full reboot or just a "warm start"?
Sent from my Galaxy Nexus using Tapatalk

What's a warm start? It seems to be doing a full reboot.. Screen goes black, then Google logo appears, then the boot animation.

It seems that I cannot do a factory reset.. selecting it in the menu brings me to the android robot on its back with a red exclamation mark, and selecting wipe data from that menu doesn't actually wipe anything even though it says it does.

Try unlocking and relocking your boot loader if you are going to factory reset anyways
Sent from my Galaxy Nexus using xda premium

It's already unlocked.. You mean locking it and unlocking again? Also, is there any way to batch reinstall all the apps tied to my account? And also, any clue how this issue could have originated? I want to avoid it in the future.

No idea.. all I can think of is an app using all of your memory as that's what causes a force close.. and sure try relocking and unlocking if a normal factory reset won't do it. If you have titanium backup you can use that to batch reinstall but if it is an all causing this issue you should install them one at a time to see of there are any adverse effects.
I don't know if it is an app but that is my best guess.
Sent from my Galaxy Nexus using xda premium

I hadn't installed any new apps prior to this.. and everything was working fine before, which is why I'm confused as to what could have caused this. Also, not just one app force closes, but like 4 at a time.. usually the Google apps for some reason. I checked the memory and the CPU and it seemed to be running at normal levels.

Have you tried an old-fashioned battery pull?
Haven't had this happen to me, but a pull usually does the trick.

Yep, and it hasn't worked.. Every time the device reboots, it will either reboot again right away, or if i don't touch it, it will idle. Then if I try to do anything, 3 or 4 apps will crash instantly, and then it will freeze and instantly restart.
If I manage to install an app, I can run it, but then it crashes and reboots again with no sign of the app. Deleting apps is also useless as they are back after reboot. Strange issue.

Guys, I really need help.. I finally had time to sit down with my phone and figure out this issue so I decided to just do a wipe. As I wrote previously, I am unable to wipe it from within the OS due to it rebooting when I do, so I decided to re-lock the bootloader.
When I typed "fastboot oem lock", it changed the lock state on my phone to locked.. as I was expecting.. however, when I rebooted the bootloader, it was unlocked again. WTF? Now I am trying to flash stock 4.0.2 to it again (which it was already), but it's been stuck on "writing 'system' ..." for half hour

Could the flash memory be corrupted somehow?

Ok, I have deduced that it is most likely corrupted flash memory.. I didn't even know that could happen, especially in 10 days.. I guess that's good ol' "Made in China" at work. Still, am I the only one who has had their flash memory fail on them?
Crossing my fingers that Rogers will replace my Galaxy Nexus even though it's rooted and bootloader unlocked :/

Hey stenzor,
I am facing same problem of rebooting...
But I haven't flashed it to yakju.
Did rogers replaced your?

[Q] Spontaneous reboots on the ZL?

Has anyone experienced any spontaneous reboots on their ZL yet?
Mine has done it twice, both times while doing things related to Google apps or accounts. The first time my phone rebooted, I was actually adding my Google account after a reset to fix the notification LED issue. When I unchecked the option to backup and restore my Google account, my phone blinked the xperia logo, then rebooted (Sony logo, xperia logo, boot animation then done). It was a very quick reboot.
The next time, I was installing apps from the Play Store. A bunch of apps were queued up, downloading and installing over Wi-Fi. I hit the home button, then was about to open up a folder to check my Gmail app settings when again, the phone blinked the xperia logo and proceeded to reboot. When it was done, it continued to install my apps as queued from the Play Store, as if nothing happened. It hasn't done it since (of course, this was only a few hours ago).
My phone is not rooted & I have not messed with the bootloader unlocking or anything. It's 100% stock while I'm evaluating it against my SGS3 for a potential permanent switch. I've got the US C6506 model (black, on AT&T -- LTE is working fine).
I really, really like this phone so far, and I'm just hoping that these two reboots were a random oddity, not to be repeated.
Interestingly, I actually fully set up the phone yesterday evening, but when I discovered I had the notification issue, I reset it this morning and re-did all of it. The phone did NOT reboot at all yesterday in the 4 or 5 hours I spent playing with it, either. It sat in standby overnight without incident as well -- all prior to the reset today & the 2 subsequent reboots.
I guess from here it'll be a waiting game to see if it does it again, but in the meantime, I was curious if anyone else had seen anything like this with their ZL.

Yup, seen it twice myself. First time, I noticed that it had rebooted when I couldn't find any previously running apps. The second time I was in the Settings screen when it randomly rebooted. I was just about to click the Display setting when this happened.
I'm just running the stock ROM on the C6506 model. I'm keeping an eye out on it and will see if there is a pattern.

rajeshr said:
Yup, seen it twice myself. First time, I noticed that it had rebooted when I couldn't find any previously running apps. The second time I was in the Settings screen when it randomly rebooted. I was just about to click the Display setting when this happened.
I'm just running the stock ROM on the C6506 model. I'm keeping an eye out on it and will see if there is a pattern.
Click to expand...
Click to collapse
Thanks ... in some ways it's good to know, and in others, it worries me. I hope it isn't a pattern, though. Thus far, I've used the phone since the two reboots without incident (music playing, bluetooth connections, and phone calls).
EDIT: A third reboot. This time I had just updated a few apps in the Play Store, returned to my home screen and was about to turn my Wi-Fi off when it rebooted. One common thread thus far is that my Wi-Fi has been on each time. I have no idea if that's related or not, though.

I have been using mine for 1 week and have not had any reboots. I am using the hspa version (c6502) and I am a heavy user

Seems to me that the random reboots are isolated to 6506 models. I haven't had one single reboot in the past week I have been extensively using mine (6502). However, while I was on CM10, my phone hung and rebooted like hell.

Yeah I'm c6502 aswell no random reboots.
Sent from my Nexus 4 using xda premium

No reboots on C6502
Same here, have been using my ZL (C6502) for the past 22 days without a single reboot or freeze. Heavy usage for last week or so (wifi on all the time). I too think this and the low call volume issue might be specific to C6506 (LTE) version.

6502 here as well, no reboots so far and I'm rooted. Been about 2 weeks.

I'm starting to think this issue is unique to me and/or my phone -- at least my specific case. Actually, I'm glad for that, because I love this phone.
I realized I may in fact have memory card corruption. I'm going to explore that further, because I had some serious issues with my SGS3 corrupting microSD cards. I thought it hadn't done it on my current card, but I have discovered some corrupted sound files on it, so I think I'm going to do a format of my microSD and see what happens.
Thanks for all the input, folks!

I had some reboots in past one week
using since March 10th
today itself had 2-3 reboots
one more thing is had blank screen during a phone call also
we need Roms for this device I never understood
why there is so much delay in release of custom Roms

Once,
but not sure it was rebooting. Cuz the screen went blank. Then i had to press a tiny yellow button that says off near the sim slot. Then it came back to life. Plus my wake up button is kinda hard to press. Do you guys hv that problem?
Sent from my C6502 using xda app-developers app

safuan7822 said:
Once,
but not sure it was rebooting. Cuz the screen went blank. Then i had to press a tiny yellow button that says off near the sim slot. Then it came back to life. Plus my wake up button is kinda hard to press. Do you guys hv that problem?
Sent from my C6502 using xda app-developers app
Click to expand...
Click to collapse
I wouldn't call that a reboot, at least not in the sense that I was seeing them. That's more like a freeze that would require a battery pull on a phone with a removable battery (I used to have this all the time on the Samsung Captivate).
My ZL was rebooting fully right in front of me (screen goes black, then the xperia logo, followed by the full normal boot sequence, just very rapid -- the boot animation is shorter than a cold boot).
Note -- I have not actually fixed my memory card yet, and I have not seen any more reboots. I'm nearly a full day on my current battery charge, too.

I have the C6506 also, and I get numerous random reboots also. I did get few logcats, but I have not seen any revelant info that causes the random reboots. I replaced my micro-sim, thinking it may caused modem panic reboots, but that wasn't root of the problem. However, I did notice that the reboots occurred less without micro SD card, but I haven't completely made that conclusion yet (I want to listent to my music!).

I also have a 6506 and have been experiencing some kind of reboot. Not a full reboot that the OP has been talking about, but one where my screen just turns off. At first I thought better battery stats was just having issues as my stats would end up all out of whack for no reason. Then today the screen shut off while in use. I only had to push the power button to get back to my lock screen. But again my stays were all out of whack. I'll have to pull the log later but I hope this is is just a software issue.

Qmann05 said:
I also have a 6506 and have been experiencing some kind of reboot. Not a full reboot that the OP has been talking about, but one where my screen just turns off. At first I thought better battery stats was just having issues as my stats would end up all out of whack for no reason. Then today the screen shut off while in use. I only had to push the power button to get back to my lock screen. But again my stays were all out of whack. I'll have to pull the log later but I hope this is is just a software issue.
Click to expand...
Click to collapse
Interesting. I've replaced all my corrupted files on my microSD card as of now, and so far, aside from that first day, I have not had a single reboot of the kind I saw before. Actually, no reboots at all, and my current uptime shows it (111 hours).
What happened to me was I had had a bad microSD card in my SGS3 -- files would become corrupted with time on it. I finally replaced it with a new one, but apparently when I copied my data back to it, I inadvertently copied a few of the corrupted audio files (notification sounds, actually) but never noticed it. I realized this when I was resetting my notification sound for text messages and heard the signs of corruption in the file, and so I began to think my phone had been responsible for the corruption. I know now that that can't be true -- otherwise I'd have some corrupt photos as well, and I don't. Only a few select sound files were bad, and because I keep regular backups of the contents of my microSD cards, I just copied the wrong ones (d'oh!).
Of course, I've had random reboots on android devices before (Asus TF101), so I'm quite wary of them -- if I see anything further, I'll post about it.

I looked at the log and saw nothing conclusive that would be making my screen turn off. I also checked my up time and it hasn't reset, so I know it's not a true reboot. When I put my SD card in I just wiped it from the phone. The only thing I put back was music files. Thinking about that now it wasn't the clean start I usually give my phones. So I just wiped the card again and we will see today if anything happens

C6503 here and I've been getting a couple reboots a day since I bought it. 2 days ago I used PC Companion to solve another issue (random loss of network signal) by reinstalling the phone software and that seems to have fixed it. Unfortunately the random reboots are still present.
I don't use any SD card at the moment.

I've now been using my ZL for a month or so, and since that first day when I made this post, no spontaneous reboots at all. I have no idea how or why, they just stopped on their own.

Weirdest issue ever! HELP NEEDED ASAP :(

Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*

It's a faulty battery mate. The phone stayed in the factory reset screen because the battery usage was basically insignificant. When you tried to go to recovery mode, the phone used more battery and boom, dead phone Happened to me too, new battery solved it.