For those with the black screen during calls and can't wake call screen...it's not perfect fix but I figured out that if your screen won't wake after pulling it away from your ear tilt it flat like it was laying on a flat surface...it wakes every time for me
HTML:
Blow compressed air into the ear piece.
Sent from my SCH-I545 using Tapatalk
thesoldier said:
Blow compressed air into the ear piece.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Its not that...works fine on touchwiz ROMs...only time I see problem is on aosp roms using ktoonsez newer kernels...he will get it ironed out soon I'm sure...but I figured I would post this to help others with same issues
Hmm I've never had that problem when I ran ktoons kernel before.
Sent from my SCH-I545 using Tapatalk
thesoldier said:
Hmm I've never had that problem when I ran ktoons kernel before.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Me either...but latest 2 kitkat builds from him have given me this issue... When I run stock cm kernel I don't have problems
jamesd1085 said:
Me either...but latest 2 kitkat builds from him have given me this issue... When I run stock cm kernel I don't have problems
Click to expand...
Click to collapse
I don't have that problem on beanstalk 4.4 ROM with KT kernel.
Everything runs great.
Just one of those things I guess.
Sent from my SCH-I545 using XDA Premium 4 mobile app
.
honkeydick69 said:
I also had proximity sensor issues... Mine turned out to be the white otter box case I have. I just used black sharpie on the case around the sensors, front camera and earpiece and it works just fine now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Interesting, so the reflection from the white was causing false readings?
Sent from my SCH-I545 using xda app-developers app
Check this post over on the CM11 thread. Lot's of folks thought it was a software problem, but turns out it's just dirty glass in front of the sensor.
Jeff
blulite said:
Check this post over on the CM11 thread. Lot's of folks thought it was a software problem, but turns out it's just dirty glass in front of the sensor.
Jeff
Click to expand...
Click to collapse
Thats CM fanboy bullsh!t. If it's dirt on the sensor it would happen on TW too. It's a software issue
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Thats CM fanboy bullsh!t. If it's dirt on the sensor it would happen on TW too. It's a software issue
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Lol
CM fanboy BS
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Lol
CM fanboy BS
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
They exist lol, won't blame anything on the code like Steve Kondik is the God of programming or something.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
They exist lol, won't blame anything on the code like Steve Kondik is the God of programming or something.
Click to expand...
Click to collapse
I expect bugs in any ROM, including stock ones. However, I must say, that I was experiencing this issue, and without changing anything software wise, I used compressed air on the earpiece, and it fixed the problem.
joshm.1219 said:
Thats CM fanboy bullsh!t. If it's dirt on the sensor it would happen on TW too. It's a software issue
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I had similar issues on TW. Did a quick Google search and found some stuff about dirty sensor. I too thought it sounded crazy, but gave it a try. When I disassembled my back-plate it was easy to see the black haze on the backside of the glass. A q-tip, alcohol, and all fixed. It worked very reliably (like new) on TW, so I decided to try CM11 again. Sure enough, the sensor worked fine with CM11. I posted over on that thread as many folks had been commenting of this problem and everyone assumed it was something broken in CM11.
Read the next handful of posts in the CM11 thread. At first a few called BS on the post, then several folks started trying it and all commented that it worked.
But again, thanks for the fanboy comment. Very constructive addition to this dialogue.
blulite said:
I had similar issues on TW. Did a quick Google search and found some stuff about dirty sensor. I too thought it sounded crazy, but gave it a try. When I disassembled my back-plate it was easy to see the black haze on the backside of the glass. A q-tip, alcohol, and all fixed. It worked very reliably (like new) on TW, so I decided to try CM11 again. Sure enough, the sensor worked fine with CM11. I posted over on that thread as many folks had been commenting of this problem and everyone assumed it was something broken in CM11.
Read the next handful of posts in the CM11 thread. At first a few called BS on the post, then several folks started trying it and all commented that it worked.
But again, thanks for the fanboy comment. Very constructive addition to this dialogue.
Click to expand...
Click to collapse
spotmark said:
I expect bugs in any ROM, including stock ones. However, I must say, that I was experiencing this issue, and without changing anything software wise, I used compressed air on the earpiece, and it fixed the problem.
Click to expand...
Click to collapse
The point is that if it works on TW without cleaning the sensor but doesn't on CM/AOSP, there's a software issue.
EDIT: not saying that cleaning the sensor wont fix it for the user, but it's like if you plug a hole in your tire.... theres still a hole in your tire.
Sent from my SCH-I545 using Tapatalk
blulite said:
But again, thanks for the fanboy comment. Very constructive addition to this dialogue.
Click to expand...
Click to collapse
Hey that's great it out figured out and you ended up helping others that's what XDA is all about..
Sometimes people's sense of humor just gets misinterpreted through simple text.
Anyways good stuff!
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
EDIT: not saying that cleaning the sensor wont fix it for the user, but it's like if you plug a hole in your tire.... theres still a hole in your tire.
Click to expand...
Click to collapse
Not trying to start a fight, and I'm certainly no fanboy, but I have to disagree with that analogy. If it is due to dust, or debris, and you remove it, there is no hole. Anyway, carry on.
spotmark said:
Not trying to start a fight, and I'm certainly no fanboy, but I have to disagree with that analogy. If it is due to dust, or debris, and you remove it, there is no hole. Anyway, carry on.
Click to expand...
Click to collapse
Lol neither am I, disagreements dont have to be fights. But if it works on one type of software but not on the other, wouldn't you say software has something to do with it?
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Lol neither am I, disagreements dont have to be fights. But if it works on one type of software but not on the other, wouldn't you say software has something to do with it?
Click to expand...
Click to collapse
I agree with that. I guess what I'm trying to say is, that people might be experiencing it for two different reasons. For some, it may be software related, for others, it may be a physical obstruction. So you can't just discount the air fix.
spotmark said:
I agree with that. I guess what I'm trying to say is, that people might be experiencing it for two different reasons. For some, it may be software related, for others, it may be a physical obstruction. So you can't just discount the air fix.
Click to expand...
Click to collapse
Fair enough , sorry if I came off wrong.
Sent from my SCH-I545 using Tapatalk
Related
Just curious if anyone has seen an improvement with a replaced phone.
I know of only one personally who has had his replaced and after two days the issue arose once again.
hey buddy, just had this happen to me right now, is it a software ? Or hardware? I restarted the phone, and it worked again... Weird!
Thanks.
Sent from my Photon using XDA App
You guys are aware it's a software issue that's already been fixed by Maintenance Release 3 available in the Development section, right ?
I'll never understand why so many people just jump the gun on getting devices replaced when 90% at least of issues are software in nature.
e-motion said:
You guys are aware it's a software issue that's already been fixed by Maintenance Release 3 available in the Development section, right ?
I'll never understand why so many people just jump the gun on getting devices replaced when 90% at least of issues are software in nature.
Click to expand...
Click to collapse
Alot of users posting this leaked release did not fix those issues.
Bandage said:
Alot of users posting this leaked release did not fix those issues.
Click to expand...
Click to collapse
Weird, it definitely fixed it for me...
Bandage said:
Alot of users posting this leaked release did not fix those issues.
Click to expand...
Click to collapse
Crud I hope the Maintenance Release 3 is not the final one if the audio problem still exists. I hope Motorola is taking their time to find all the problems reported and fix them before officially releasing a maintenance release.
Bandage said:
Alot of users posting this leaked release did not fix those issues.
Click to expand...
Click to collapse
Funny because I haven seen one post to back up this comment
Sent from my MB855 using XDA App
e-motion said:
You guys are aware it's a software issue that's already been fixed by Maintenance Release 3 available in the Development section, right ?
I'll never understand why so many people just jump the gun on getting devices replaced when 90% at least of issues are software in nature.
Click to expand...
Click to collapse
Probably because they want to. It was their money don't worry about it. I dont know why some jump the gun to run their mouth about stuff that isnt any of their business.
I was asking as the OP on this thread because I actually use my phone as a phone for communicating and not just playing games on it.
Kinda negates having a specific phone of it locks up and or has silent calls....so if it made sense to exchange it I would....so that I could actually use the tool I bought....ya know?
I initially had the same issue. Turned out I still had my old phone powered up. Once I turned it off and rebooted all was fine.... Maybe this works for you...
Sent from my MB855 using XDA Premium App
phyba said:
Funny because I haven seen one post to back up this comment
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Check the thread in the dev section. Korey(WDM) posted that its still happening to him
Sent from my SPH-D700 using XDA App
It's still happening for me after the update, but its not even a officially released update so can't blame moto for that update not fixing it lol
Sent from my MB855 using XDA Premium App
Mine seems to be fixed after calling sprint... Dunno what they did on their end.....
Sent from my MB855 using Tapatalk
I just tried turning off the enhanced voice privacy that someone else said made it better for them. Hopin for the best...mine had seemed to happen more after mr3
Sent from my MB855 using XDA Premium App
I replaced m y phone today at Best Buy and so far so good.
Strange thing is, while this is a MR1 software package, there sure are some things which are different.
The email setup for one to manually configure was completely different than my first phone.
The rear speaker is way louder than the first unit and I thought that one was loud.
The really weird part is, as soon as I opened the browser the first time and then went to load bookmarks, all of my previous bookmarks were already there. Is Google or Sprint storing this information in a cloud somewhere?
I was so taken back by this that I checked all of the various serial #'s and such to make sure they gave me the new phone, even though I watched them with it the entire time.
BTW....setting the battery to PERFORMANCE really speeds this up on this phone.
jfenton57 said:
Just curious if anyone has seen an improvement with a replaced phone.
I know of only one personally who has had his replaced and after two days the issue arose once again.
Click to expand...
Click to collapse
Download APP Cache Cleaner. It fixed my issue without reboot or MR5. Hope that helps and "thanks" please
Just picked up the Photon yesterday and I think I had my first silent call this morning. Phone rang, answered and neither party could hear the other. Has sprint acknowledged this as a known issue?
Only had that issue before I flashed the latest sbf
Sent from my MB855 using XDA Premium App
After going through 3 from 2 different sources, I gave up and went back to another phone till something reliable as a phone comes out.
I have the latest software build and I still have the same problem
THIS THREAD IS CLOSED: Get your updates here: http://forum.xda-developers.com/showthread.php?t=1574718
So do calls work on this one?
afrojoc said:
So do calls work on this one?
Click to expand...
Click to collapse
Yes, yes they do.
So is the modified phone.apk included or should we flash it separately since you said "download separately"?
Sweet!!! Anyone willing to test?
Sent from my SAMSUNG-SGH-I777 using XDA App
ddominator said:
So is the modified phone.apk included or should we flash it separately since you said "download separately"?
Click to expand...
Click to collapse
Nope it is included, I will clarify that in the first post.
ddominator said:
So is the modified phone.apk included or should we flash it separately since you said "download separately"?
Click to expand...
Click to collapse
I think its already included since he said *used*
Thanks for this brother. I will give it a shot right now because I'm a loser and I have nothing else better to do.
I've been running this for two days with Entropy's work on the kernel and the phone.apk
Calling works, just a little muffled sometimes.
I'm downloading right now, although I'm sure it's the same exact thing I've already done w/ the modem n kernel together.
Amazing work!
Sent from my GT-I9100 using xda premium
Looking forward to trying.
taking the plung
VERY NICE!!! I hated tw ics. It hurt playing around with it. So glad you took the time to port it. I'll keep it for a day or two, oh i see my screen just came on. LOL ! besides that it seems pretty solid.
This works fabulously! My only question is how do I get all my apps and settings back if I used titanium. It says I'm not rooted
Sent from my GT-I9100 using XDA App
sounds just like Entropy's BabyPacifier...
Yes! Progress!
Calling works and I confirm as others have reported- it is a little muffled (outgoing voice). Also, I cannot seem to adjust the volume down while using speakerphone. It seems to be on max.
Thank you Fenny!
Sent from my GT-I9100 using xda premium
Willing to give it a shot. Thanks for sharing.
Duffman14 said:
sounds just like Entropy's BabyPacifier...
Click to expand...
Click to collapse
Many have posted ports in that thread to keep the bugs found easier but this is without TW, so lets see how this goes.
Duffman14 said:
sounds just like Entropy's BabyPacifier...
Click to expand...
Click to collapse
that was tw ics this is asop ics
Are you sure screen turns on and off? I flashed aokp this morning and having noticed anything
Sent from my GT-I9100 using xda premium
Duffman14 said:
sounds just like Entropy's BabyPacifier...
Click to expand...
Click to collapse
You should probably read the OP again bro. This is AOSP. The one entropy posted is touch whi
LiLChris06 said:
I was thinking the same, many have posted ports in that thread to keep the bugs found easier.
Click to expand...
Click to collapse
Like Todfather said, this is aosp.
Sent from my GT-I9100 using xda premium
I mean graveyard & doornail dead!
I know I read several had the big problem that I have now.
Seems like there were a fair amount of bricks. Our close calls anyway on many devices.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Why this particular weekend?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
sholsten said:
I know I read several had the big problem that I have now.
Click to expand...
Click to collapse
How did you brick your phone
sent from my lovely phone....hmmm wait its a tablet...waaa i dont really know.....im PARANOID NoW!
baudilus said:
Why this particular weekend?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I've been scratching my head on this all weekend.
King71st, I flashed Liquid JB on it and used Flap's kernel and it didn't work so good yesterday.
All the bricks I've seen is using the wrong rom for the device. There are many variants to most phones and they use a rom for the variant they
don't have
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
All the bricks I've seen is using the wrong rom for the device. There are many variants to most phones and they use a rom for the variant they
don't have
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Yes, but why so many on THIS weekend. I think a wrong ROM was accidentally posted as an i717 or something.
I bricked an i727 with a rom thru goo manager which I'm sure was not posted correctly. Will never use it or rom manager again. I Don't trust them.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
I bricked an i727 with a rom thru goo manager which I'm sure was not posted correctly. Will never use it or rom manager again. I Don't trust them.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I liked it for named backups, but flashing CWM just to use the app is scary when you dont see your specific device listed.
sholsten said:
Yes, but why so many on THIS weekend. I think a wrong ROM was accidentally posted as an i717 or something.
Click to expand...
Click to collapse
I believe this to be true, I've flawed a ton of sh!t that was for another phone but in our forums. My 3 notes have proved un brick able in my hands (knock on wood).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
LittleRedDot said:
I believe this to be true, I've flawed a ton of sh!t that was for another phone but in our forums. My 3 notes have proved un brick able in my hands (knock on wood).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Mine had been unbreakable from when I bought it in June till yesterday.
sholsten said:
Mine had been unbreakable from when I bought it in June till yesterday.
Click to expand...
Click to collapse
How did you fix yours? Tried flashing abyssnote and liquidsmooth and it wont turn on. Torch blinks when you hold lock for about a minute.
I may have worded that wrong. I haven''t fixed mine. I meant it has been good since I bought it til I put Liquid JB on it Saturday afternoon. Mine is dead as dead can be.
any help fixingmine would be appreciated. searched but nada. desperately googling at the moment
scjsean said:
any help fixingmine would be appreciated. searched but nada. desperately googling at the moment
Click to expand...
Click to collapse
I'm just like you, but I believe Samsung is our only hope
scjsean said:
How did you fix yours? Tried flashing abyssnote and liquidsmooth and it wont turn on. Torch blinks when you hold lock for about a minute.
Click to expand...
Click to collapse
you flashed stuff for the Note 2; THAT is why you now have a brick
sholsten said:
I'm just like you, but I believe Samsung is our only hope
Click to expand...
Click to collapse
No jtag is your only hope.. Sending a brick into Samsung is fraud. You claim all responsibility when you give your phone root access, not to mention installing a 3rd party operating system.
True there are ways to revert everything to stock so that you can return it, but these are for people with legitimate hardware defects not to be abused by someone who can't man up and admit they made a mistake.
Ffs
STOP CONDONING FRAUD ON THIS FORUM!!!
THE REASON COMPANIES WANT TO LOCK DOWN DEVICES AND MAKE US NOT ABLE TO TO MODIFY ANYTHING IS THAT EXACT REASON.
TAKE RESPONSIBILITY FOR YOUR OWN MISTAKES AND STOP RUINING IT FOR THE PEOPLE THAT KNOW WHAT THEY ARE DOING!!
XDA does not condone Fraud in any way, shape or form. If you broke it and somehow pull the wool over their eyes, don't post it here.
We all take these risks when we flash the ROMs/Kernels/Mods. In doing so, we also should take the responsibilities as well.
I am still trying to figure out why "This weekend" as well as the relevance of this thread.
I love the way it looks on other devices.... is there anyway we could possibly get it ported or otherwise get it to run on the Thunderbolt?
I wouldn't even care if it had data... just the camera and display... I have an extra Bolt and would love to use it as a iDroid.
je2854 said:
I love the way it looks on other devices.... is there anyway we could possibly get it ported or otherwise get it to run on the Thunderbolt?
I wouldn't even care if it had data... just the camera and display... I have an extra Bolt and would love to use it as a iDroid.
Click to expand...
Click to collapse
Patience is a virtue. . @disconnecktie
jonah1234 said:
Patience is a virtue. . @disconnecktie
Click to expand...
Click to collapse
I'll take that as it is on it's way... Thank You
je2854 said:
I'll take that as it is on it's way... Thank You
Click to expand...
Click to collapse
I've been helping jblack with a pretty big project recently but once that is posted I'll be back on paranoid android.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I've been helping jblack with a pretty big project recently but once that is posted I'll be back on paranoid android.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
@disconnecktie I am seeing you everywhere AND on a lot of projects..... Thanks for being such a great dev.
I know you are working on CM9 BUT I would take PA over any ROM any day. If you could push PA up in the queue there just might be some
Pepsi/Caffiene/alcohol/your choice of poison in abundance headed you way :b
P.S. Pepsi is my choice of drug is the only reason why I said that lol
Lol well I have a semi working port already but calling doesn't work properly atm. It makes the call but the mic or speaker don't work in call yet. I'm going to rebase it off of the cm9 that jblack and I have been working on once it is more stable.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Lol well I have a semi working port already but calling doesn't work properly atm. It makes the call but the mic or speaker don't work in call yet. I'm going to rebase it off of the cm9 that jblack and I have been working on once it is more stable.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
could I possibly get a copy of that? I want it for my iDroid I use for work... We aren't allowed phones but CAN have music.
I don't want the rebase just the one that semi-works :b
Check you PMs
Sent from my ADR6400L using Tapatalk 2
Netflix
Does Netflix work on any of these builds you guys are working on? I am running the multi-source aosp from twistedumbrella and that's one of few things that don't work on it.
bedward1229 said:
Does Netflix work on any of these builds you guys are working on? I am running the multi-source aosp from twistedumbrella and that's one of few things that don't work on it.
Click to expand...
Click to collapse
Not a high priority atm. Getting the kernel and data squared away are a little higher on the list but we're going to address it once we have time. I think its either a drm issue or a dhcp issue. At any rate, in my testing I was able to get it to play audio but video still wouldn't play so it may be a codec issue. I guess if you like to listen to movies you're all set
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Not a high priority atm. Getting the kernel and data squared away are a little higher on the list but we're going to address it once we have time. I think its either a drm issue or a dhcp issue. At any rate, in my testing I was able to get it to play audio but video still wouldn't play so it may be a codec issue. I guess if you like to listen to movies you're all set
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Haha that's a good start though. I don't think it's a big deal really, even if it never works its definitely not a deal breaker I was just curious. It's cool that you guys are still working on it, thanks for what you do.
I should be taking care of what we talked about yesterday... I have the Sasba ROM with 4EXT on it now...
disconnecktie said:
Not a high priority atm. Getting the kernel and data squared away are a little higher on the list but we're going to address it once we have time. I think its either a drm issue or a dhcp issue. At any rate, in my testing I was able to get it to play audio but video still wouldn't play so it may be a codec issue. I guess if you like to listen to movies you're all set
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
So you're telling me you don't just listen to movies all day on Netflix?
jonah1234 said:
So you're telling me you don't just listen to movies all day on Netflix?
Click to expand...
Click to collapse
Well of course I do... That's why it's on the back burner duh.
Sent from my ADR6400L using Tapatalk 2
Hi All
Although i tried lots of things (Modifying the system file , cleaning regularly) my phone keeps ghost clicking.
Yesterday it made to the top and take itself to Airplane mode and i was not aware and waiting a call..
I really need help or advices ...
Thank You
What firmware are you on?
LordManhattan said:
What firmware are you on?
Click to expand...
Click to collapse
I am on the latest firmware. Without any mod. only rooted.
kirpi_e said:
I am on the latest firmware. Without any mod. only rooted.
Click to expand...
Click to collapse
maybe search for a post by @hamdogg about editing build.prop to change the sensitivity
blueether said:
maybe search for a post by @hamdogg about editing build.prop to change the sensitivity
Click to expand...
Click to collapse
I think its about the file under system/usr changing the touch sensivity. I have already done it. No luck , still ghost clicks...
kirpi_e said:
I think its about the file under system/usr changing the touch sensivity. I have already done it. No luck , still ghost clicks...
Click to expand...
Click to collapse
Hmmm.. Are you sure there isn't a piece of pasta on your screen? It's a big screen after all
Yes, I'm drawing a blank here Have you tried to flash a different ROM?
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
Hmmm.. Are you sure there isn't a piece of pasta on your screen? It's a big screen after all
Yes, I'm drawing a blank here Have you tried to flash a different ROM?
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
I regularly clean my screen but ofcourse in daytime there are times it is dirty
I did not try to flash a different ROM but i am not sure if this is a hardware issue or software..
It seems hopeless because i saw other people experiencing same. Also there was a movie in You tube, a guy put a service report from SONY
saying that telephone is Ok no issue , but he was turning on the phone and as soon as phone booted it started ghost clicks..
Ah sony.. you used to be the symbol of quality for me once..
kirpi_e said:
I regularly clean my screen but ofcourse in daytime there are times it is dirty
I did not try to flash a different ROM but i am not sure if this is a hardware issue or software..
It seems hopeless because i saw other people experiencing same. Also there was a movie in You tube, a guy put a service report from SONY
saying that telephone is Ok no issue , but he was turning on the phone and as soon as phone booted it started ghost clicks..
Ah sony.. you used to be the symbol of quality for me once..
Click to expand...
Click to collapse
I had this problem too (like many others) when we were on 532, but it was fixed on 257. You could flash a AOSP ROM and see if it's still the same? If it's not, it's a software issue, and if it's still there, it's probably the hardware. My guess is it's a software issue.
You could try a CM ROM or the GPe. The latter is the most stable one and without bugs.
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
I had this problem too (like many others) when we were on 532, but it was fixed on 257. You could flash a AOSP ROM and see if it's still the same? If it's not, it's a software issue, and if it's still there, it's probably the hardware. My guess is it's a software issue.
You could try a CM ROM or the GPe. The latter is the most stable one and without bugs.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
LordManhattan, thank you for your replies. I will try to do as per you advise. I will write back the result here.
Thank you
kirpi_e said:
LordManhattan, thank you for your replies. I will try to do as per you advise. I will write back the result here.
Thank you
Click to expand...
Click to collapse
do you have a screen protector on it? if so take it off and reapply. Possibly something interfering with it.
hamdogg said:
do you have a screen protector on it? if so take it off and reapply. Possibly something interfering with it.
Click to expand...
Click to collapse
I don't have a screen protector. Do you think it is helpful?
kirpi_e said:
I don't have a screen protector. Do you think it is helpful?
Click to expand...
Click to collapse
when you are in the sun, and it reflects off your ultra (turns into a mirror) do you see any discolouration? like some of the screen is dirty?
Not that its dirty, but it could be the coating on the screen thats starting to come off.
hamdogg said:
when you are in the sun, and it reflects off your ultra (turns into a mirror) do you see any discolouration? like some of the screen is dirty?
Not that its dirty, but it could be the coating on the screen thats starting to come off.
Click to expand...
Click to collapse
No i do not see but i can notice the dirt on the screen, but when i clean with a soft cloth then it becomes very clean and nothing can be seen.
kirpi_e said:
No i do not see but i can notice the dirt on the screen, but when i clean with a soft cloth then it becomes very clean and nothing can be seen.
Click to expand...
Click to collapse
... then the options you have are to try different firmware, to see if its software... or take it in to where you bought it as it could be hardware.
Just my 2 cents, if cleaning the screen doesn't work and updating to 290 doesn't, if you have a third party keyboard disable it and return to stock then see if any change.
Sent from my C6833 using XDA Premium 4 mobile app
SpyderTracks said:
Just my 2 cents, if cleaning the screen doesn't work and updating to 290 doesn't, if you have a third party keyboard disable it and return to stock then see if any change.
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I use Swype without any problems.
hassanmahmood said:
I use Swype without any problems.
Click to expand...
Click to collapse
Yeah, I'm saying for him, not for you
Sent from my C6833 using XDA Premium 4 mobile app
SpyderTracks said:
Yeah, I'm saying for him, not for you
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
lol - I know - but I figure since we have the same device - the problems ought to be relatively universal.
hassanmahmood said:
lol - I know - but I figure since we have the same device - the problems ought to be relatively universal.
Click to expand...
Click to collapse
I had an issue with ghost clicks after enabling Swiftkey tablet legacy after having had a completely click free experience for months before enabling it. As soon as I disabled it it was fine and has been ever since. Weird I know, but maybe worth trying.
Sent from my C6833 using XDA Premium 4 mobile app
hello all again
I think i solved my issue. I found out another topic in another Xperia phone forum. That phone's users problem was undersensitive touch screen , so i did opposite of what they did
I went to /system/usr/idc but not modified the file max something.
I modified clearpad.idc file. The value touch.pressure.scale was 0.0075 something. I changed it to 1
now the touchscreen is less responsive and nearly no ghost clicks anymore.
Hope this helps anybody have this issue.