Develop Bugs

[Q] different volume bug, same thing or broken phone

have i got the volume bug if my phone hangs and then reboots every time i touch volume up or down when the screen is on? Samsung insist that its the same thing and i need to wait for the update but i can't see anyone else describing that the problem causes a reboot, and my volume has never actually turned down on it's own as far as i can tell.

That sounds different altogether.
Sent from my Galaxy Nexus using XDA App

matt2053 said:
That sounds different altogether.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thats what i suspect. Its just a pain to have been waiting for 4 days for something that probably wont fix anything and then to have to start the whole thing over again with samsung. O well

stanleywinston said:
have i got the volume bug if my phone hangs and then reboots every time i touch volume up or down when the screen is on? Samsung insist that its the same thing and i need to wait for the update but i can't see anyone else describing that the problem causes a reboot, and my volume has never actually turned down on it's own as far as i can tell.
Click to expand...
Click to collapse
Deal with the retailer you bought the phone from, and get a replacement from them.

oscillik said:
Deal with the retailer you bought the phone from, and get a replacement from them.
Click to expand...
Click to collapse
I'll give it a go. Im guessing they wont do a doorstep swap like i'd get from t mobile though. Hopefully i wont be without it for long. In our short time together i've grown quite attached to this phone (and almost got used to not touching the volume button)

Couple of questions (you may have already done these -apologies if you have)
Have you tried a factory reset? If not, maybe worth trying it, could be an app doing wierd things.
Also, try running a logcat trace when replicating the issue - see if it helps point in the direction of the issue.
Does the phone still crash when you're in the bootloader? (This _may_ help to rule out application related issues)

I have tried a factory reset. Weird thing is that im pretty sure that it didnt do it for the first few hours that i was playing with it. It was just at the point that i had it all set up that i first noticed it so assumed it was a rouge app and did a factory reset. When it rebooted i signed in and hit volume and it crashed so its definately not an app.
I almost believed that it was the normal volume bug because if i go somewhere more remote in the house, away from all electrical stuff, i can hammer at the buttons for a while before it crashes so maybe ive just got a more extreme version of the bug. Just noone else seems to have anything close. Volume control works fine in a call and when the screen is off but i havent tried in bootloader yet. I'll give it a go

[Q] Issue after ICS update - Phone freezing

After the ICS update on my non-rooted phone, the phone seems to be freezing
up and becoming unresponsive. After a while it looks like the radio "resets", all
the icons disappear in the top bar (signal, wifi, data) and it shows no service.
Then slowly one by one they all come back and I can use the phone again.
Sometimes I receive the "System is not responding" dialog box, but not always.
There is not one particular program it is doing this in, it can be something as
simple as pulling down the notification bar that will cause the freeze.
Any suggestions are appreciated, I couldn't find anyone else with the same issue.
Thanks.

Try:
Turn off phone
Take out SIM
Put SIM back
Turn on
I've had my phone act weird with respect to signal, wifi and data when this was the issue. Worth a shot, at the very least.

Digital_Buddha said:
Try:
Turn off phone
Take out SIM
Put SIM back
Turn on
I've had my phone act weird with respect to signal, wifi and data when this was the issue. Worth a shot, at the very least.
Click to expand...
Click to collapse
Thank you for the response.
Tried this and had the system is unresponsive issue right on reboot. If I do a
factory reset, does it reset to the current firmware or what was originally on the
phone (probably a really stupid question). I wonder if some other program isn't
ICS compatible and is doing something in the background. Doesn't look like
anyone else is having this same issue.

jdscully said:
Thank you for the response.
Tried this and had the system is unresponsive issue right on reboot. If I do a
factory reset, does it reset to the current firmware or what was originally on the
phone (probably a really stupid question). I wonder if some other program isn't
ICS compatible and is doing something in the background. Doesn't look like
anyone else is having this same issue.
Click to expand...
Click to collapse
If you do a factory reset and it was the standard Kies legit update from Tmo, it won't downgrade your phone - will just re-install a fresh copy of your ICS. Did you do a restore of apps from your last version (gb?) with data? That could cause problems I would think..

VoiD_Dweller said:
If you do a factory reset and it was the standard Kies legit update from Tmo, it won't downgrade your phone - will just re-install a fresh copy of your ICS. Did you do a restore of apps from your last version (gb?) with data? That could cause problems I would think..
Click to expand...
Click to collapse
Yes I did the legit update on Kies, standard stock phone un-rooted.
Do I need to backup pictures before the reset, its been a while since
I had to do this.
At this point, I think its worth a try to wipe it clean and clear out all the
data.

jdscully said:
Yes I did the legit update on Kies, standard stock phone un-rooted.
Do I need to backup pictures before the reset, its been a while since
I had to do this.
At this point, I think its worth a try to wipe it clean and clear out all the
data.
Click to expand...
Click to collapse
wipe the dalvik cache and cache then reboot

I did a factory reset and that solved the issue.
Thanks for all the assistance.

I've done a factory reset and wiped the cache more than once already and i still get a force close or unresponsive, enough that its really irritating me now. Any advice? And also, when texting, the typing responds very slow.
Sent from my SGH-T989 using XDA

itsdamage said:
I've done a factory reset and wiped the cache more than once already and i still get a force close or unresponsive, enough that its really irritating me now. Any advice? And also, when texting, the typing responds very slow.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Are you letting it sit for like 10 minutes during first boot after factory reset then reboot again before setting up. Its likely that some scripts are running from the initial installation and you need to let it rot until its done..

I did exactly that, thanks for the advice. Hoping that may fix the problem. I wiped the cache and factory reset, then let the phone sit for a good while before going through the play store and re-installing everything.

This issue just resurfaced again. The last 2 days I am getting the freezing, radio reboot and android process not responding.
No one else having this issue?

I think I'm in the same boat. I was stock GB, and just did the mini OTA update (which was great). A few days later ICS became available via Kies from T-Mobile, and I "upgraded".
Since the upgrade my phone is laggy, screen is significantly less responsive and also my battery life is less than before.
I have NOT done a factory reset of my phone yes (plan on doing that today), but even with that I have read that performance does not improve.
Ideally, I would love to return back to the stock tmobile gb firmware. However, even after literally 2 hours of reading I can't find the "how-to" and files I need.
I would appreciate any assistance.

t989 chip lags
ive notice this happen on my tmobile galaxy s2. i think it has to do with the Qualcomm chip on tmobiles stock roms.
When i had sprint i bought my girlfriend a galaxy s2 on the sprint network which runs the samsung exynos chip. She never complained about any lag or freezing whatsoever. I then left sprint because of their garbage network and joined tmobile.
bought 2 galaxy s2s and i noticed the lag almost immediately. The phone has random lag spikes as well as freezing and force closes. It had it on stock gingerbread and it has it on stock ICS too.
My girlfriend complains about freezing all the time so i decided to root her phone too. Right now im testing DarkSides v7 rom and if its pretty good in performance i will flash her phone with it too. So far it has been pretty snappy and everything works.

jdscully said:
This issue just resurfaced again. The last 2 days I am getting the freezing, radio reboot and android process not responding.
No one else having this issue?
Click to expand...
Click to collapse
Yes i have the exact same problem...and the clock goes off too...if i don't reboot then this will keep happening...if you go into settings then development settings and tick off only let 4 process run in the background it should stop...try it and let me know
Sent from my SGH-T989 using xda premium

tonydetroit said:
I think I'm in the same boat. I was stock GB, and just did the mini OTA update (which was great). A few days later ICS became available via Kies from T-Mobile, and I "upgraded".
Since the upgrade my phone is laggy, screen is significantly less responsive and also my battery life is less than before.
I have NOT done a factory reset of my phone yes (plan on doing that today), but even with that I have read that performance does not improve.
Ideally, I would love to return back to the stock tmobile gb firmware. However, even after literally 2 hours of reading I can't find the "how-to" and files I need.
I would appreciate any assistance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1668502
follow that first post. i went through exactly the same problems and found this guide and am now happy again and running stock GB on my Galaxy S2.
Because you are on stock ics (im guessing you are..), you can just follow that guide and flash the UVLDE update.

Yes clock resets to standard standard time.. I already did a factory reset and worked done for a couple weeks. My wife has same phone and she is getting the freeze ups now.

jdscully said:
Yes clock resets to standard standard time.. I already did a factory reset and worked done for a couple weeks. My wife has same phone and she is getting the freeze ups now.
Click to expand...
Click to collapse
Yeah really sux...it's random..I'm using a custom kernel and still having that problem....
Sent from my SGH-T989 using xda premium

Yup here too. Almost reminds me of XP. Really ticking me off & it never happened on gingerbread. Rooted now & before I'm on rogers 4.0.4. wondering if there's going to be fix? Haven't seen if Google / rogers /at&t have commented?
Sent from, The Eclectic Chair.

I'm getting the freezes as well even after doing a factory reset.
It sucks, I'm waiting for cyanogen to release a stable release and then I'm switching.

djtheraven said:
Yes i have the exact same problem...and the clock goes off too...if i don't reboot then this will keep happening...if you go into settings then development settings and tick off only let 4 process run in the background it should stop...try it and let me know
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, I'll give it a try. But it really shouldn't be necessary on a phone that's got more going for it than the stock nexus that 1st came out with ics.
There's something else going on.
Sent from, The Eclectic Chair.

[Q][Help] Phone constantly "reboots", stock firmware, have logcat!

Alright, so my girlfriend's Samsung Galaxy S II started to go through these weird partial reboots several weeks ago (maybe even months). The phone would randomly go black, play the stupid shutdown/startup (dont remember which) jingle...then just simply be at the lock screen with a crossed out circle where the signal bars would be (for just a couple of seconds). When this happened, I used to just tell her to shutdown the phone, take out the battery, and let it sit for about 30 seconds, then put everything back together and start it back up. This seemed to work, which made me think it might have just been a software or at worst a memory issue of some kind.
This issue was always intermittent, but now, no matter what I do, it just keeps looping this "restarting" problem. I can't access any internal memory space from my computer because in the time it takes to connect, it just "reboots" again. I made a logcat of the phone up until the "reboot", and in doing so noticed that when I would browse the phone via adb shell, I saw no mount for the sd card...which then lead me to believe maybe it was an issue with that. I checked the sd card for corruption (and prior to even using it, checked that all blocks were read/writable (legit)), but that led nowhere.
Anyways, not having any idea where to go next, nor where to begin or what to look for in the 5000+ lined logcat, I turn to xda with hopes of getting some sort of help. Thanks in advance for any I get!
EDIT: Oops, some other important notes I didn't mention (other than in title); this is running stock firmware, only OTA. I tried once to upgrade her to ICS via Kies, but the upgrade would never complete. She also refused to let me root her phone...so unless there is a stock recovery mode, her phone has none...

bump, as its been a week and no responses. If anyone has any ideas or can figure out whats wrong from the logcat, please help.

Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...

EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Sent from my SGH-T989 using Tapatalk

EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?

Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.

For starters, thanks everyone for the responses! After this long, its really great to see so many in one day!
richardlibeau said:
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Click to expand...
Click to collapse
Thats what I thought, because it seemed to get exceptionally hot before "rebooting"...at first...then I was noticing it "rebooting" when clearly cold. If it is indeed overheating like I had thought in the very beginning, is there anything I can do about it? What does it use for heat conductivity and displacement? And for that matter, I would think if it was overheating though, it would actually reboot, not the half-ass semi-reboot its been doing...
And what is wakelock exactly that it would cause an issue? Only apps I see using it are WootWatcher, KeyguardViewMediator and PowerManagerService.
krazierokz said:
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Click to expand...
Click to collapse
I would use odin...but the phone doesn't stay on long enough to do much of anything before "rebooting". Also, she is already using stock firmware + OTA updates. And her contacts are not what I am worried about, its her photos and such. This is the very reason why I hate internal memory for phones...
And I'm pretty sure its not a sticky power button, I had seen that being a common issue when researching before posting. And again, if I have not been clear, its not exactly "rebooting", just semi-rebooting; phone starts up, crap starts running, a min or 2 later, phone acts like its restarting (plays sound and all), then just comes back to the lock screen immediately...I can't really describe it much more than that.
And no, I'm not familiar with "download mode"
bzlik88 said:
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Click to expand...
Click to collapse
Ya, like I said in the reply above this, I don't think its the sticky power button problem...but I could always be wrong. I only didn't mention over heating because I felt I did a good job of ruling it out.
DeliciousLimeJuice said:
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
Click to expand...
Click to collapse
Its running GB atm, never updated to ICS via Kies...

I wish I could help you further but i can say one thing, the rebooting that your describing is called a "hot reboot". I know what ur talking about and others will too if u use that term. Good luck.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

[Q] Problem since root

I finally rooted it yesterday and it now is very unresponsive at times. It will get to the point where it's frozen for about 30 seconds before it does anything. I flushed the caches and did a reset, same thing. So I flashed Jedi ROM on it. It's a little better but still has moments where ti freezes for a time. Is there a fix for this?

Rooting does absolutely nothing to the performance of the device. Its comparable to giving yourself admin rights on a windows computer. No performance change just extra features. Might want to check any apps that you installed after rooting

I did not install anything after root.
It works smooth as silk with the stylus. Possible sensitivity adjustment?
Maybe the sdcard needs to be reformatted?

marksm said:
I did not install anything after root.
It works smooth as silk with the stylus. Possible sensitivity adjustment?
Maybe the sdcard needs to be reformatted?
Click to expand...
Click to collapse
ROOT will not brake the phone or cause lag. it changes nothing internally except rights to your phone. no tweaks or files deleted. I can see it being something with the screen since you say the pen works great and using your finger I assume it micro stutters. but even the freezing for 30 sec does not sound screen related. I would wipe and format data, and then try another Rom. I used jedi from the first build all they up to 15 and it ran like a champ. its something you are doing, or have not undone yet.

I would suggest clearing caches. Its got nothing to do with rooting, but neither does rooting have to do with lag.
It sounds like an app was restored with data.

rangercaptain said:
I would suggest clearing caches. Its got nothing to do with rooting, but neither does rooting have to do with lag.
It sounds like an app was restored with data.
Click to expand...
Click to collapse
Agreed....
Excellent point ranger.....TY.....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

no apps were restored either. When I flashed the new ROM I cleared every cache I could see listed and wiped it clean. All I can think of is the old stuff on the sdcard is causing issues so tomorrow I will reformat it and reset again.

Well then, the only thing I can think of is you flashed an incorrect kernel. What exactly did you flash?

Used the root tool from http://galaxynote2root.com. Odin and cwm6-root-note2.tar.
It still had the bad lag and freezing after I un-rooted it and restored the original ROM.
I have since flashed Jedi, didn't like it and now am on NOTEorious Prime.
What I have noticed is that the lag and freezing go away when I am connected to a wireless network. Maybe it screwed up my modem?

And have you verified the APN settings as being correct ?
Or they may simply be mixed up by default..
It may be set on ATT LTE.....instead of ATT PHONE for example...
Both will work...but one will drop the network speed by about 70%...
Just a thought....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

Perhaps a factory reset from within recovery --- to make all settings default. By now there's a lot of stuff floating around in there.

Why would the original root change the APN settings.
I have factory reset several times. Even with the factory image applied fresh, it still freezes. The weird thing is, it responds just fine to the stylus.
I am at the point where I restore the stock ROM again and take it to ATT to see if they will swap it out.
Thanks for the help, keep the ideas coming..

Flashing a custom rom or recovery or kernel voids your warranty. Please don't tell us about plans to return the phone to at&t. The phone worked as expected before you began flashing.

It's not the radio or wireless either. It works perfect with the stylus but seems like it doesn't detect my finger to operate normally. Does Samsung have a tool to reset the display sensitivity?

There is a dial code for the touch screen. I don't know it, but I've found those codes by googling 'android secret note 2 dialer codes' or something like that.

Looks like I have it fixed.. It's working right since I followed the instructions here http://android.stackexchange.com/questions/39423/galaxy-note-10-1-does-not-recognize-finger-touch
I had installed swiftkey so I removed that and tried swype beta and it's all good now.

I restored everything back to stock and it is still having problems. The screen is unusable with my finger, I have to use the S Pen for everything.
Would reloading the stock ROM with kies be different than using Odin? Does Samsung put some key piece of code in the areas that get changed with rooting?
I am at a loss..

marksm said:
I restored everything back to stock and it is still having problems. The screen is unusable with my finger, I have to use the S Pen for everything.
Would reloading the stock ROM with kies be different than using Odin? Does Samsung put some key piece of code in the areas that get changed with rooting?
I am at a loss..
Click to expand...
Click to collapse
Ok to test you touch screen etc. type this in code in your dialer *#0*#!!
And don't think Sammy would put something in there, to make there phones not work correctly!
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4

Bajanman said:
Ok to test you touch screen etc. type this in code in your dialer *#0*#!!
And don't think Sammy would put something in there, to make there phones not work correctly!
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Click to expand...
Click to collapse
On the test screen, I have to tap screen many times until it finally registers. Then I drag my finger around for about 30 seconds before it starts picking up and filling in the boxes. It will finally let me fill in all the boxes and say it passes but it takes a lot of effort.

marksm said:
On the test screen, I have to tap screen many times until it finally registers. Then I drag my finger around for about 30 seconds before it starts picking up and filling in the boxes. It will finally let me fill in all the boxes and say it passes but it takes a lot of effort.
Click to expand...
Click to collapse
Yeah it's not suppose to be that difficult honestly. Something is defiantly wrong!!
Me personally if you bought the phone from an AT&T store! I'd reborn it for a replacement! And if it's not used from someone off the street. Then I'll put it back to fully stock, reset flash counter. Then return and replace at one of there local service centers. Especially if it's giving that much problems as it sounds to be doing. Seems as if the screen has some hardware issues inside...
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4

Touchscreen problems

So I am having this problem since 4.4.3 and 4.4.4 update. Once or twice a day the screen won't respond to touch. Should I use a custom kernal or this might be a hardware problems.
Sent from my Xperia U using XDA Free mobile app

Ameer Shimoga said:
So I am having this problem since 4.4.3 and 4.4.4 update. Once or twice a day the screen won't respond to touch. Should I use a custom kernal or this might be a hardware problems.
Sent from my Xperia U using XDA Free mobile app
Click to expand...
Click to collapse
How do you fix it when it happens? Do you have to restart? Does the touch fail or does the tablet freeze?
Honestly not very sure what you could do, besides maybe trying a factory reset? That would work if a software problem.
What about cleaning it and removing any screen plastic guard.

U can say it freezes then I have to restart it. This is happening after two factory resets.
Sent from my Xperia U using XDA Free mobile app

Firmware fix: http://forum.xda-developers.com/showthread.php?t=2428133, read and follow the op very carefully.
...if it does not help, or you think it may be internal:
http://forum.xda-developers.com/showthread.php?t=2535835

mdamaged said:
Firmware fix: http://forum.xda-developers.com/showthread.php?t=2428133, read and follow the op very carefully.
...if it does not help, or you think it may be internal:
http://forum.xda-developers.com/showthread.php?t=2535835
Click to expand...
Click to collapse
OK I'll try..
Sent from my Xperia U using XDA Free mobile app

Same issue here, I think.
Just purchased a refurbished Nexus 7 (official factory refurbished) from Amazon. My touch screen works great for a day or so, but eventually touch stops working altogether and sometimes requires a hard-reboot (holding the power for 10-seconds). Downloaded a touch screen test app which works great (even with ten fingers on the screen), tracking well on all parts of the screen. It's just like the touch atrophies over time until it stops working.
First thing I did to the tablet after getting it was to unlock the bootloader and load stock/rooted 4.4.4. Is there some way to update the touchscreen firmware that I'm missing?
I don't want to open this thing up and muck with the hardware for fear of damaging it. I'm holding out hope that there is a software fix, because rebooting fixes it right up.

nebhead said:
Same issue here, I think.
Just purchased a refurbished Nexus 7 (official factory refurbished) from Amazon. My touch screen works great for a day or so, but eventually touch stops working altogether and sometimes requires a hard-reboot (holding the power for 10-seconds). Downloaded a touch screen test app which works great (even with ten fingers on the screen), tracking well on all parts of the screen. It's just like the touch atrophies over time until it stops working.
First thing I did to the tablet after getting it was to unlock the bootloader and load stock/rooted 4.4.4. Is there some way to update the touchscreen firmware that I'm missing?
I don't want to open this thing up and muck with the hardware for fear of damaging it. I'm holding out hope that there is a software fix, because rebooting fixes it right up.
Click to expand...
Click to collapse
Look 2 posts up from yours.

mdamaged said:
Look 2 posts up from yours.
Click to expand...
Click to collapse
Oops - I looked at the link to the hardware fix, but not the firmware fix. Thanks, I'll give this a try first.

Firmware fix above seems to have alleviated the issue for me. At least I haven't seen the issue over the last several days, which is good news. Hopefully that holds up over the long term. :good: