Develop Bugs

Mango users, watch out for unresponsive touchscreen

Title says all. I was just chillin' listening to some music (Let's Get It to be exact) and when I pressed my power button to check and see how fast the WiFi reconnects, I swiped up and nothing happened. It was like that for about a minute or two, the volume rocker worked and I could hold down the camera button and go to the camera, but the touch screen just wouldn't work. I popped off the back and was about to remove the battery and thats when everything went back to normal...pretty odd...just a heads up.
Wifi now reconnects instantly. I am pleased

strange... not had any problems like this at all on mine yet...
Seems VERY responsive, been using it all lastnight over and over and this morning.
what phone you have? im using the mozart

Keefo said:
strange... not had any problems like this at all on mine yet...
Seems VERY responsive, been using it all lastnight over and over and this morning.
what phone you have? im using the mozart
Click to expand...
Click to collapse
Dammit, I thought I said what phone I was using...I'm on the HTC Arrive. It hasn't done it since I've posted..I highly doubt it'll happen all the time (probably won't ever happen again)..just wanted to mention it.

This happened to my arrive right as it was done updating on the screen that says the update is done...the close button wouldn't work, but I remember reading this thread so I waited it out and it started to work after like 2 min

I am having the exact problem on my HD7, only seems to occur if I am listening to music. The lock screen appears, but I cannot swipe.
Mine doesn't always come back and I have to remove the battery.

I have the same issue every once in a while. I'm not on Mango though, I'm running NoDo on a HTC Surround.
It's happened about 5 times in the last six months.

I've had the same issue since before NoDo. The quickest fix is to try turning the screen off and then on again, sometimes it takes a few attempts but it normally works.

haven't noticed on dvp or anything I wonder if its a htc thing...

I haven't noticed it, though I did get the red screen associated with changing the reg entries to get 32 bit color one.
Interesting side not, when I was updating to Mango, on one of the reboots I got the red screen and thought I was screwed, but the update process continued and on the next reboot it was normal again...

ms79723 said:
Title says all. I was just chillin' listening to some music (Let's Get It to be exact) and when I pressed my power button to check and see how fast the WiFi reconnects, I swiped up and nothing happened. It was like that for about a minute or two, the volume rocker worked and I could hold down the camera button and go to the camera, but the touch screen just wouldn't work. I popped off the back and was about to remove the battery and thats when everything went back to normal...pretty odd...just a heads up.
Wifi now reconnects instantly. I am pleased
Click to expand...
Click to collapse
nope havnt come across this yet on my Samsung Focus. The only issue seems to be the increased boot up time(phone stays on d Samsung logo screenfor a long time) but I am quite sure its due to Samsungs crappy bootloader and besides I hardly have to reboot WP7 ever anyway

Hey, has anyone else noticed that weird icon where your signal and data icon should be?
Idk if its the new icon for no signal or what...but when I unlocked my phone, I saw an icon that looked like the copy and paste icon where my signal and data icon should be.

I must say I'm noticing this on third party apps a lot, I don't know whether it's because they are downloading data from the Internet or what but it's happening quite a bit at the moment. LG Optimus 7 btw.

Loss of Service:Fix(kinda) test

Hey as everyone knows there are some people having LOS and it will remain that way until after a reboot. First I'm rooted but not with a custom kernel. I'm on the stock kernel(just flashed CWM and then root.zip) So I have had LOS a few times since I got my phone. Just a few minutes ago I got LOS after a phone call and it remained that way. AbsolutZeroGI on IRC wanted me to try something whlile I had LOS before I rebooted. I went into the task manager, selected the ram tab and then pressed the clear button. That didnt bring service back but after I did that I did get the roaming notification(but still had LOS) so I plugged my phone into my PC(not to try to fix it but to boot into recovery) and then I noticed my signal came back without a reboot as soon as I plugged in the cable. Now I'm not really sure if/why plugging in the USB would correct this or if it was just a coincidence or if it fixed it. Although I know the other times I had LOS it didnt come back until a reboot no matter how long I waited.. So I would like to run a test..
The next time you get LOS go into the taskmanager, select the ram tab and then click clear, then plug your phone into your PC (Edit: While your screen is off). Did your signal come back or do you still have LOS?
EDIT:
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.

Thank you in advance for everyone who tests this out for us. If we can find a real method that works every time we can start working on a temporary fix until Sammy gives us a firmware update so LOS won't be so bothersome.

i have not experienced the los, but have experienced very poor signal when trying to connect to the net. but when i rebooted the signal did get better

Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.

plmiller0905 said:
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
Click to expand...
Click to collapse
Hmm maybe I'll install the stock kernel and see of that fixes it. I only had my phone since yesterday and it was rooted after an hour or so of having it and since I've had at least 5 Los. :-( but I have read the same that people claim its happening to them as well without ever rooting
Sent from my SPH-D710 using XDA App

I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium

I've had my phone since launch day. I didn't root until the 20th. I had no LOS in that time I was completely stock. Right after I installed bubby's CWM and root the problems started. I mean the same night. It had happened several times until I went back to the stock kernel. I have since had the LOS for literally 5 seconds while it switched from Sprint to roaming and service was right back. Not a problem since. I'm not saying these other kernels are the complete problem and that the phone is not without bugs. I just think that maybe the other kernels make the problem (if any) worse.
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
jirafabo said:
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The other night I had 5 times in two hours. Literally!!

I'm completely stock and picked up my phone on Launch day. I had several LOS during the first few days. I updated my PRL, Profile, Firmware etc. and it hasn't been an issue since.
I do have an issue roaming, as in my phone wont.

Ok guys, I'm going to update the OP but here is a new development.
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.

graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
I saw that theory from someone else around here as well. Definitely seems like something is going to sleep and not coming back on and the modified kernels seem to exacerbate the issue for some reason. (Maybe the source Samsung released is older than what the phone shipped with and the issue was improved between the two versions?)

Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!

graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
That wouldn't work, because in reality, the phone checks cell towers for new calls something like every 5-10 seconds. No sleep for the wicked radio.
No. It is definitely something that disables the radio entirely.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
plmiller0905 said:
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
Click to expand...
Click to collapse
There's no reason not to root the phone now AT ALL.
The current root method of:
1) Install custom recovery+kernel,
2) Flash su binary,
3) Flash stock recovery+kernel
---
The current root method does nothing but add files to /system partition -
you change nothing else in the operation of the phone but add root privileges.
Flashing roms while they are in beta though, that's just asking for trouble, unless you are testing for the rom builder.

I have the LOS icon at this very moment, yet I just received a call? Also, I plugged it into my computer, but nothing changed.

Hi all. I just had LOS and tried to use my car charger instead of my computer. It didn't fix the issue but I did notice that the charging led wouldn't illuminate. after reboot the phone gets signal and the led is working fine. I don't know if that is significant but wanted to mention it.
Sent from my SPH-D710 using XDA App

Interesting thread. Ive had mine for 3 days now and havent experienced this at all.
Sent from my SPH-D710 using Tapatalk

about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?

I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium

leond said:
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
Click to expand...
Click to collapse
No, but that is major suckage, happens to me once a day. Makes me want to punch babies.
los, which I get too, is when you get the no smoking signal instead of a cdma signal.

I went to root+stock kernel and the problem is gone and LOS is gone to

txmikester said:
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There was no update when these phones were released. If she was activating the phone then she was 9/10 referring to a profile update and prl update which each phone does when being activated.
Sent from my SPH-D710 using xda premium

[Q] Galaxy Nexus keeps turning OFF

I have a problem with my Galaxy Nexus turning OFF at night.
I goto bed at night and open the clock app and click the screen to dim it. When I wake up in the morning the phone is OFF. I have to pull the battery in order to boot. The battery is fully charged.
I returned the phone after this happened twice and received a brand new one. I have the same problem with this new device. I have changed the power socket and the charger yet still the problem persists.
Is anyone else experiencing similar problems?
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.

Try it without any off your apps installed. If the problem goes away you know it's an app causing the problem. Then start adding them back in batches until the problem re-occurs. Eventually you'll narrow the issue down to one app.

mark_w said:
I have a problem with my Galaxy Nexus turning OFF at night.
I goto bed at night and open the clock app and click the screen to dim it. When I wake up in the morning the phone is OFF. I have to pull the battery in order to boot. The battery is fully charged.
I returned the phone after this happened twice and received a brand new one. I have the same problem with this new device. I have changed the power socket and the charger yet still the problem persists.
Is anyone else experiencing similar problems?
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Click to expand...
Click to collapse
This is happening to me too.
At random times, the phone will refuse to wake from sleep.
Nothing but a battery pull will fix it.
I don't have skype installed.

Have a look at this:
http://forum.xda-developers.com/showthread.php?t=1360880&highlight=sleep+of+death

Mine started today. Really hope this does not keep happening or I need to return this right away. Missed a few phone calls today and didnt realize until I looked down any my phone was just simply black. Will not wake up or do anything at all. You have to pull the battery. Right before this happened my data was dropping non stop about every 5 minutes for an hour.
I'm trying to stay calm because I love this phone, but between the data drops and the phone turning off im loosing patience quick.

This is happening to me as well. With TWO different phones. The first one I returned to Verizon and now its happening on the second one.
Phone will power off while doing random tasks. The two I've noticed is browsing on the stock browser and texting on the stock texting app.

I'm having the same problem. It's happened twice in the 3 days I've had the phone. It hasn't happened while I'm using it, both times it was when the screen was already off -- it just wouldn't waku up. Nothing short of pulling the battery, letting it sit, then powering on would work.
Couldn't have come at a worse time either, my daughter is in the hospital and I get updates from the surgeons via phone. So now I have to check every 5 minutes and make sure the phone is still on.
Phone is bone stock, out-of-the-box.
Sent from my Galaxy Nexus using Tapatalk

i just had my first turned off this morning... my friend's SGN happened 5 days ago too. very unreliable....

I had that happen to me as well. Turns out I forgot that I had an app scheduled to do a backup at like 3 AM.
Sent from Galaxy Nexus
CodenameDroid 1.2 cdma & Franco 14.4

My sgn turned off every night now. Anyone got any ideas why? I turned my verizon backup already.

reboot durring skype call
mark_w said:
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Click to expand...
Click to collapse
it does it when i have skype running too. also i have other other audio apps open. (power amp, tunein, pandora) It's happened twice to me and each time it has been during a skype call while the other apps were running. (in widget form)

shock sensitive in the area right below the camera?
My device just "randomly" switches off (sometimes several times a day). After a long search for a reproducible cause, it seems safe to say that at least some devices seem to be extremely shock sensitive in the area right below the camera (on the back of the device). Even minuscule shocks to this area switch these devices off. Youtube-user 'jardinepatten' demonstrates this problem nicely in a video called "Galaxy Nexus Turning Off".

problems with a refurb

hey all-
youve been a great community since ive been around (last december) and i was wondering if anyone had any insight on a problem im having.
I recently got a replacement phone that is refurbished from sprint, because the power button on my old e4gt was completely stuck
when i got the phone i immediately rooted it and went to my usual set up of Blazer 4.1 with the rogue 1.4.1 kernel.
since then ive been having some trouble:
the touchscreen is very wonky, ill be in the middle of texting and it will all of a sudden start selecting things all over the screen. simply turning the screen off and then back on usually works, but ive noticed that the frequency of this is increasing. also the menu home back and search keys all pick and choose when they want to work, and when they dont. sometimes ill press them and they wont work, other times ill be browsing the web and the menu button will start going off and on, without me pressing it.
ive also been experiencing quite a few random reboots, this wouldnt be such a problem however sometimes the phone will just shut off, with the red led light still on, but the screen wont come on when i press the power button. ive also noticed that sometimes the phone will randomly reboot, and then hang on the samsung screen. this has happened a few times at night and caused me to miss class because my alarm didnt go off (lol). when any of this happens i just hold down the power and vol up button to reboot into recovery, and then reboot the phone from there.
the only visible difference i can tell is that under the build number it says: "Blazer v4.1 ~ PI:FG-X^2I^2
i dont remember the last part of that being in any of the previous build numbers; ive been running this build pretty much since it came out, theres just something about the speed, snapiness, and battery life of this gb build that has me hooked.
if anyone knows if these problems are hardware related, or if i just had a bad flash, id greatly appreciate your feedback.
i know this has turned into a long post, but i just have one more question:
i use google play music as my music player, and absolutely love it. my favorite part about it is the fact that i can "download" songs to stay available even when i dont have a data connection, this comes in reallyyyy handy. HOWEVER, i use titanium backup to backup my apps, and when i flash to a new rom and restore play music, it restores all my music, but not the music that i have stored on the device. this is annoying because i then have to wait for a stable wifi connection to download the 500 or so songs that i usually keep on the device. My question is whether or not there is a way to backup all of the cached music, or if i could move the app+app data to my sd card, so i wouldnt have to redownload all the songs when i flash a new rom.
again youve all been a great community and im thankful for all the devs and all the work they do. i apologize for this post being so long, i dont usually post much but when i do ive always gotten the solutions for the problems ive had.
have a great day everyone, and you stay classy san diego

replace
put the phone back to stock and see if these problems still occur. If the do still occur then take it into a service center and have it replaced

ryandoubleu said:
put the phone back to stock and see if these problems still occur. If the do still occur then take it into a service center and have it replaced
Click to expand...
Click to collapse
i wish i could take it to a service center however when i had the battery out of it someone spilled water on the battery so the water damage sticker is now red even though the water never got on the phone.

Brick it and get a new one. They messed up.
Sent from my SPH-D710 using xda premium

Ctanferno22 said:
i wish i could take it to a service center however when i had the battery out of it someone spilled water on the battery so the water damage sticker is now red even though the water never got on the phone.
Click to expand...
Click to collapse
A service center should take the phone apart and check the sticker in the inside. You could also just buy a battery from amazon and use that when taking it in.
sent from MY BAD A$$ ET4G

Will sprit replace a brick phone. Cause I know if you try tweak it and f it up that your fault.
Sent from my SPH-D710 using xda premium

Get android assistant from play. It will allow you to move apps to your SD card. Tools>App2SD
Buy a new battery and send that back with the phone if you continue to have issues

s2 bricked it self?

I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?

autonami said:
I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?
Click to expand...
Click to collapse
Sounds like the power button may be stuck which is a known issue with this phone. Here is a thread on the issue:
http://forum.xda-developers.com/showthread.php?t=1931310

autonami said:
I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?
Click to expand...
Click to collapse
I've come to find out if the phone crashes this will happen, it's normal behavior believe it or not. If you will be patient and wait for about 7 to 10 minutes, the phone will finally reboot. The next reboot will be normal time again. This might be the device's way of protection, IDK.

cwyman said:
Sounds like the power button may be stuck which is a known issue with this phone. Here is a thread on the issue:
http://forum.xda-developers.com/showthread.php?t=1931310
Click to expand...
Click to collapse
thanks, this did the trick. but i think it may have been more so the volume up button. there is a metal piece that surrounds the volume button on the board, somehow it was coming off, pushed it back on and mashed the buttons a bunch, came right on.

autonami said:
...it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly...
Click to expand...
Click to collapse
This is almost certainly caused by a bad/stuck power (on/off) switch. It's a very common problem on all the US-carrier Galaxy S2 models. (Sprint, Boost, Virgin, Telus, T-Mobile, AT&T, etc. I don't think Verizon sold the SII)
You can check the switch by gently touching the physical switch (plastic cover/"button" removed) with a toothpick/pen/etc. As a "snap-action" switch, it shouldn't activate until you hear/feel it "snap" closed. If it's activating with a light/slight/tiny touch, the switch is bad. On my Sprint GS2, even the slightest brush against the power button caused it to wake the phone. Sometimes it would stick "on", and then the phone would reboot. I bought a new switch, soldered it in, and have no problems since.
If you don't have insurance coverage and are out of warranty, you can replace the switch yourself. Several eBay sellers offer replacement power switches for the SGH-T989 Galaxy S2. (about ten bucks)
Or, if you don't have mad soldering skills, several offer mail-in repair service as well, and most seem to have great feedback.