Develop Bugs

Weird touch screen glitch...

Ok so I realize that this is almost positively a hardware issue, however I just wanted you guys' opinion. So its happened 1 or 2 times before but a simple reboot has fixed it usually, until today when it has gotten really bad all of a sudden. The issue is that randomly, my phone will act like it is being touched on the screen and will either select something or not let me touch what I'm trying to touch. In fact as I'm typing this with the phone's keyboard my phone keeps thinking I'm touching the discard button (which I'm not, obviously) And I've noticed that its always in the bottom left corner of the screen in portrait mode. This is causing me to sometimes not be able to move icons or unlock the phone or scroll through pages because the phone thinks I'm like multi touching the screen in the corner. This happened for a while earlier this week until I pulled the battery. Then this morning it got terrible enough that I could barely use my phone at all even after multiple reboots and fixing permissions. I even went so far as odining back to stock EC05 and OTA updating to EL30, from EG22. ( haven't had time to update to an official build until now. ) again it obviously isn't a software issue but I don't know what I should do, like get a new epic (which I really don't want to) even though this hasn't been a problem until very recently and I don't remember anything damaging my phone. Anyways just thought I'd share my problem with you guys to get any suggestions. And sorry for how long the post is.
Sent from my SPH-D700 using XDA App

wazzuup199 said:
Ok so I realize that this is almost positively a hardware issue, however I just wanted you guys' opinion. So its happened 1 or 2 times before but a simple reboot has fixed it usually, until today when it has gotten really bad all of a sudden. The issue is that randomly, my phone will act like it is being touched on the screen and will either select something or not let me touch what I'm trying to touch. In fact as I'm typing this with the phone's keyboard my phone keeps thinking I'm touching the discard button (which I'm not, obviously) And I've noticed that its always in the bottom left corner of the screen in portrait mode. This is causing me to sometimes not be able to move icons or unlock the phone or scroll through pages because the phone thinks I'm like multi touching the screen in the corner. This happened for a while earlier this week until I pulled the battery. Then this morning it got terrible enough that I could barely use my phone at all even after multiple reboots and fixing permissions. I even went so far as odining back to stock EC05 and OTA updating to EL30, from EG22. ( haven't had time to update to an official build until now. ) again it obviously isn't a software issue but I don't know what I should do, like get a new epic (which I really don't want to) even though this hasn't been a problem until very recently and I don't remember anything damaging my phone. Anyways just thought I'd share my problem with you guys to get any suggestions. And sorry for how long the post is.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have had this happen... wasn't a hardware issue for me, but it may be for you... I fixed it by turning off the screen (locking the phone) and cleaning the screen off thoroughly.... it fixed the issue... it may not fix it for you though... hopefully its that easy... for me it was some dirt or something on the screen making it "think" I was touching that spot when I wasn't... hope that's all it is for you...
Sent from my SPH-D700 using Tapatalk

Out of curiosity does this only occur while charging or always?
Sent from my SPH-D700 using XDA App

It happens always. On and off the charger. And I don't think its that easy as I had a screen protector on it and I thought it could be something like dirt under the screen protector causing it to freak out but I took off the protector and its still happening. Looks like I need a replacement... ):
Sent from my SPH-D700 using XDA App

wazzuup199 said:
Ok so I realize that this is almost positively a hardware issue, however I just wanted you guys' opinion. So its happened 1 or 2 times before but a simple reboot has fixed it usually, until today when it has gotten really bad all of a sudden. The issue is that randomly, my phone will act like it is being touched on the screen and will either select something or not let me touch what I'm trying to touch. In fact as I'm typing this with the phone's keyboard my phone keeps thinking I'm touching the discard button (which I'm not, obviously) And I've noticed that its always in the bottom left corner of the screen in portrait mode. This is causing me to sometimes not be able to move icons or unlock the phone or scroll through pages because the phone thinks I'm like multi touching the screen in the corner. This happened for a while earlier this week until I pulled the battery. Then this morning it got terrible enough that I could barely use my phone at all even after multiple reboots and fixing permissions. I even went so far as odining back to stock EC05 and OTA updating to EL30, from EG22. ( haven't had time to update to an official build until now. ) again it obviously isn't a software issue but I don't know what I should do, like get a new epic (which I really don't want to) even though this hasn't been a problem until very recently and I don't remember anything damaging my phone. Anyways just thought I'd share my problem with you guys to get any suggestions. And sorry for how long the post is.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
its a software issue. it happened to me a little while after flashing to custom roms. odin back to ec05 , reroot, then try flashing the dexodexed el30 rom and see if it does the same thing.
---------- Post added at 05:24 AM ---------- Previous post was at 05:23 AM ----------
LORDFIRE00 said:
its a software issue. it happened to me a little while after flashing to custom roms. odin back to ec05 , reroot, then try flashing the dexodexed el30 rom and see if it does the same thing.
Click to expand...
Click to collapse
if it was hardware, you wouldn't have even been able to type your post from your xda app.

[Q] s3 stuttering/twitching

I have tried searching for this problem but I must be using the wrong terms... so sorry in advance if I missed a post that addressed this issue.
My sprint S3 does this twitchy/glitching thing on every touchwhiz based jellybean rom (does not do it on TW ICS ROMS) I have tried. It basically makes it nearly impossible to do sliding animations, IE it can actually get stuck and start flashing halfway between screens, or when pulling down the top menu, however you can open new programs just fine if you are already on the right screen for them. Luckily it does not do this all the time, but when it happens it keeps doing for 10 minutes or so and its annoying as hell.
I figured this must be a rare issue even though it effects both my wifes phone and mine, since I have never read anything about it, however I just got a new replacement phone and it does the exact same thing, even on dead stock TW JB ROM.
Oddly enough I discovered last night that if I turn on my screen filter app it stops completely, but it starts right back up when I turn off screen filter..... any ideas how to fix this?

Try grabbing cache clear from the play store and set it to run every 12 hours. It helped my phone a good bit.
Sent from my SPH-L710 using xda premium

No one else ever has this issue?

joelespinoza said:
No one else ever has this issue?
Click to expand...
Click to collapse
I had it dude, but it was just on the CleanBean ROM, it was annoying as hell!
So I changed the ROM, Its weird that its happening on a Stock ROM, any suspicious app?

Call&Note Recorder disables when screen is turned off

Hey guys, im kinda new here, i've lurked and gotten help but this is my first post.
I was using Call&Note Recorder for a few days, everything worked super well was recording everything and all that, but last night i noticed that the icon wasn't in the notification bar up the top. So i went into it, reactivated it, but everytime the screen goes off, it disables it again, whether its from locking, or putting it up to my ear.
This (of course) is really annoying, i don't know if anything else is broken as this is just the start, but i don't know what i did in the last few days that i could of broken it. I did install Xposed framework and Keepchat, which didn't seem to work for me, so i've since uninstalled it. Besides that i can't think for the life of me what could be causing it.
So i am hoping someone here knows, and might be able to help without having to restore it.
Thanks in advance. Scott.
EDIT: ok it happens with Dropsync as well, if i start a sync and lock the phone, it shuts it compleatly down. I really need help
EDIT 2: Was unable to get into recovery either, the Galaxy Note II logo would come up and then fritz out and reset, and just keep doing that over and over. So currently re-installing stock firmware with odin, in the hopes that i fix it.
EDIT 3: When i flash the stock firmware, everything works as it should, if i reroot it, the same problems arise. Things turn off when locked and no able to enter recovery. I really hope someone has an answer for this, as its driving me insane working it out.
Is there ways to check what i've installed root wise and uninstall it?

[Q] Graphic glitches and other problems

So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it

greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.

meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...

bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.

[Q] Black screen on calls

I rooted my girlfriend's S3 with no problems. I can install a TW rom and everything works as expected. If I installed a ASOP rom, when a call is made or received the screen turns off. If you pull the phone away from your ear the screen stays off. I've browsed around the forums, but have not found anything to resolve the issue. Any ideas of what might cause this on ASOP roms ?
Thanks in advance,
Richard

Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.

You could test the proximity sensor response. It might be flaky?
I use this app,
https://play.google.com/store/apps/details?id=com.tbs.activity
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

audit13 said:
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
Click to expand...
Click to collapse
The only time it has been an issue is with ASOP roms. If I use a TW rom, there is an option to leave the screen on during a call. This is what I clicked to get the screen on during calls. However, with ASOP roms there is not an option for this. I don't think it's the proximity sensor since the screen stays on with calls on a TW rom. I forgot to mention that the ASOP was KK rom, but I have the same phone different cell provider and do not have this issue. I think I tried a JB rom with the same effect.

When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?

audit13 said:
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
Click to expand...
Click to collapse
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.

riche1 said:
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
Click to expand...
Click to collapse
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.

audit13 said:
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
Click to expand...
Click to collapse
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!

riche1 said:
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
Click to expand...
Click to collapse
Without making any changes to the stock TW ROM dialer settings, does the screen go black when you place the phone next to your ear and come back on when you move it away from your ear?

If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?

riche1 said:
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
Click to expand...
Click to collapse
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.

audit13 said:
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
Click to expand...
Click to collapse
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard

riche1 said:
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
Click to expand...
Click to collapse
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.

audit13 said:
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
Click to expand...
Click to collapse
she said it was not a problem until the phone was updated to 4.3 through ATT software update. This was way before I rooted the phone. The same thing started with her sister's phone. So.. I'm stumped as to what the problem could be. I rooted it because I thought CM11 might fix the issue and that was not the case. I don't know how I can go about fixing it. I don't want to take a chance in bricking the phone.