Someone just passed to me an a100, it seems nice and all, rooted and unlocked it, now on reaper relix.
My problem is i am experiencing touch breaks, if i were to swap between pages i am experiencing some weird problem.
I downloaded a drawing app to test it, and if i try to draw a line without lifting my finger i notice that the line breaks.
Any workaround?
rain987 said:
Someone just passed to me an a100, it seems nice and all, rooted and unlocked it, now on reaper relix.
My problem is i am experiencing touch breaks, if i were to swap between pages i am experiencing some weird problem.
I downloaded a drawing app to test it, and if i try to draw a line without lifting my finger i notice that the line breaks.
Any workaround?
Click to expand...
Click to collapse
Unfortunately this is an issue with the A100, some have the issue others don't(mine does). It seems to be a grounding issue or that is what the general consensus is.
No way to really fix it, if you have a cover taking it off may help, and trying different ways of holding it may help as well.
Yeah. Mine has it too. Using with no case and holding it with 2 hands makes it better. Also using it while plugged in stops it too. Those are the only workarounds I know of.
thanks this made it clear, was think i need to overclock it, but seems more like a manufacturing issue.
i have maxed out my thanks, will thank both of you in the morning.
Guys try cm10 b2. I no longer have those annoying breaks when scrolling. I did a clean install.
*can someone link me gapps or just playstore. Hard to find it using tab.
FromDeA100
rain987 said:
Guys try cm10 b2. I no longer have those annoying breaks when scrolling. I did a clean install.
*can someone link me gapps or just playstore. Hard to find it using tab.
FromDeA100
Click to expand...
Click to collapse
Get goo manager from the play store you can get then latest gapps there
Sent from my Galaxy Nexus using Tapatalk 2
Thx but I already got it from ur cm10 general thread.
FromDeA100
Was going to post the links but since i'm a new user apparently I cant. Arg.
Related
I'm not sure if this was asked already but, I was wondering If someone could fix the multi touch issues of the mytouch slide. It has the same exact problem as the nexus one/htc desire etc etc.
Problem -- http://www.youtube.com/watch?v=qzhUzq6bTPg&feature=player_embedded
The LG optimus one seems to have a work around for it and i was wondering if someone could bring that workaround to our phone. http://www.youtube.com/watch?v=5Ur9n9pQUAg
Same!!
Did you ever solve this problem. I'm having the same issue because I can't pull down the notification bar and also whenever I switch to another screen the notification bar comes down lol. But other have fixed this problems somehow with a kernel
tylert5 said:
Did you ever solve this problem. I'm having the same issue because I can't pull down the notification bar and also whenever I switch to another screen the notification bar comes down lol. But other have fixed this problems somehow with a kernel
Click to expand...
Click to collapse
I really wish i could solve it haha, and yea crazy stuff like that happens sometimes. Multitouch is definitely also a problem with 3d shooting games. I was actually hoping a dev try to fix this problem. If there is a fix/workaround for other phones, then its definitely possible on this phone.
Nothing you can do. It is the sensor in the phone. It was never meant for multi-touch
UberMario said:
Nothing you can do. It is the sensor in the phone. It was never meant for multi-touch
Click to expand...
Click to collapse
I'm not sure if you've clicked this link that was posted in the OP http://www.youtube.com/watch?v=5Ur9n9pQUAg, but it shows a clearpad2000 device with a mostly fixed multitouch axis. According to the OP in this thread, its done by inverting the inverted axis http://forum.xda-developers.com/showthread.php?t=933686
I was checking out those links. Seems that those fixes are only half working.
It really is a hardware problem. They're just recompiling the kernels to clean it up so that it looks like it works properly, but even in the videos it's evident that there's some messing up. If I'm reading right, our phone probably has the same controller as the G1 and N1. And newer phones don't have the problem because they have better hardware.
Yes I realize this is a hardware problem and that this is not a complete fix, but its better than not having any kind of fix at all.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
I had the same problem, was really annoying when playing multitouch games like PewPew because it would sense your fingers opposite of where they were and the axis locked during multitouch which makes fine movements impossible. The newer 4 and 5 point multitouch screens perform way better.
I'm running CM10 nightlies for a while now my camera has been failing. Everytime I try to take a picture, after a couple of seconds, it just freezes. Has anyone had this and tried fixing it?
So turns out that Smart Stay is causing the problem because it is trying to access the camera the same time I am trying to use it. So to fix it I just added any app that uses the camera to the exception list option in smart stay. Finally an end to this annoying problem. (or is it? ...I really hope it is.)
I had the same problem until I switched to jelly bean jellybomb rom instead. Try it, u will love it
Galaxy0523 said:
I had the same problem until I switched to jelly bean jellybomb rom instead. Try it, u will love it
Click to expand...
Click to collapse
I'll definitely give it a try, but what about if I still want to use cm10? Has anyone had any progress fixing this problem or at least finding the source of it?
In the changelog for cm10 it says the next nightly will introduce a "Fix Ignore Keyevents", maybe, just maybe, that will help!
Many people do not have this problem. Are you sure its not something you installed?
Sent from my SPH-L710 using xda app-developers app
pastert33 said:
Many people do not have this problem. Are you sure its not something you installed?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have odined back to stock, and wiped&&formatted everything possible. I did come across a thread (the link I have since lost) that mentioned something about possibly gapps causing the problem. Just know I had the idea that maybe because I am using JustinBean's inverted gapps there is a problem. I will investigate and see if that helps.
I can't believe I didn't think of this sooner. So even after the update, no change.. still freezing - GREAT! So then I started getting really aggrivated and started to uninstall apps that "Pimp My Rom" included, and I thought flash might be the culprit. And then it hit me, this is a camera problem right? Well then what app uses the camera? SMART STAY of course, and it made even more sense because it takes a sample at a certain interval and that explains that I am able to use the camera only for the short amount of time (always the same amount of time). So to fix the problem I just set in the exception list in smart stay an exception for any app that uses the camera. I really hope this is the fix I need. Thanks for your input guys!!
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse
My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse
mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse
No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear
Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.
It's not all notes.
Sent from my SGH-T889 using xda premium
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over
Hey there,
Unfortunately I have another problem with Liquid Smooth. I tried searching this bug with no luck. The screen flickers rainbow stripes (best way I can describe it) when I launch the camera from the lock screen, when I hit the power button on the lock screen and occasionally when I go into settings. Any ideas why this could be? or is it just a know bug? This happened much more infrequently on 2.2 but still happened.
Let me help you rack up 10 posts, and then go ask in the thread as this is rather rom specific. If anyone in there is able to recreate it after you post, then it's an issue with the rom itself
CNexus said:
Let me help you rack up 10 posts, and then go ask in the thread as this is rather rom specific. If anyone in there is able to recreate it after you post, then it's an issue with the rom itself
Click to expand...
Click to collapse
Much appreciated thanks buddy!
arkgrotto811 said:
Much appreciated thanks buddy!
Click to expand...
Click to collapse
do I just reply to myself 10 times or will that not work? I mean you are welcome to copy my question into the thread if you want. the flickering isnt really an inconvenience to me I just want to bring any issues I find to light!
arkgrotto811 said:
do I just reply to myself 10 times or will that not work? I mean you are welcome to copy my question into the thread if you want. the flickering isnt really an inconvenience to me I just want to bring any issues I find to light!
Click to expand...
Click to collapse
Do you do anything to make it flicker or does it just do it randomly? Clean install? Good download?
------------------------
Sprint Galaxy S3
Whiplashh Rom
Look it up. :trooper:
arkgrotto811 said:
do I just reply to myself 10 times or will that not work? I mean you are welcome to copy my question into the thread if you want. the flickering isnt really an inconvenience to me I just want to bring any issues I find to light!
Click to expand...
Click to collapse
Just keep replying, and check to make sure you did what Whiplashh mentioned
Whiplashh said:
Do you do anything to make it flicker or does it just do it randomly? Clean install? Good download?
------------------------
Sprint Galaxy S3
Whiplashh Rom
Look it up. :trooper:
Click to expand...
Click to collapse
1) It just happens randomly as far as I know, but only on when I do the things I listed.
2) On 2.2 I did a clean install, updating to 2.3 I did a dirty. But it still happened on 2.2, 2.3 just made it happen more often.
3) Yea downloaded using goo, flashed with TWRP as per usual
arkgrotto811 said:
1) It just happens randomly as far as I know, but only on when I do the things I listed.
2) On 2.2 I did a clean install, updating to 2.3 I did a dirty. But it still happened on 2.2, 2.3 just made it happen more often.
3) Yea downloaded using goo, flashed with TWRP as per usual
Click to expand...
Click to collapse
One more postttt
Issue seems fixed now. Completely factory reset and reinstalled a few hours ago. Seems to be working fine! Weird how it was happening before update though as well and then happened more frequently after. Thank you Whiplashh and Cnexus for your help!
I think this is just a problem with cm/aokp/aosp type roms. CarbonRom did the same for me.
Sent from my SPH-L710 using xda app-developers app
I am experiencing the same issue with the LiquidSmooth 2.4 for Verizon. I recently did a clean install this weekend and everything was fine until the screen started flickering randomly. The flickering looks like white noise with different colors lined up horizontally. The only constant to this issue seems to be tied to the stock android messaging app.
Have you guys tried going into developer options and ticking that H/W option I think that's what's its called lol haven't been on aosp in a while but that helped my issues when I had it
Sent from my HTC One using xda premium
AT&T S3, Clean flashed 2.3, dirty flashed 2.4. I agree with the SMS app being involved. Happens once I open it, particularily when sending/viewing an MMS. Force closing the app seems to fix it.
jazz995756 said:
Have you guys tried going into developer options and ticking that H/W option I think that's what's its called lol haven't been on aosp in a while but that helped my issues when I had it
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hey thanks i was having this issue on my verizon gs3 and checking disable HW overlays is deloper settings seems to have fixed it
I had a Note 8 for a short time which had this issue but ive noticed it on my gpad 8.3 v500 when its in landscape.
The issue is when im scrolling the screen one side lags behind the other if you do it quickly enough...so if i do it Up and down it gives a wobble effect. Noticable in netflix too.
Has anyone had this? Im hoping its a jellybean issue as i said my note 8 was the same.
Not a deal breaker but it does bug me.
What rom are you on?
Sent from my iPhone using Tapatalk
EdenGottlieb said:
What rom are you on?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Stock .....ive not changed anything since purchase
wantefc said:
Stock .....ive not changed anything since purchase
Click to expand...
Click to collapse
Have you installed any background-running apps that may cause this problem? I don't know what can cause screen stuttering like you have. Have you thought about installing CM? It works great and is 1000 times faster than stock
Sent from my iPhone using Tapatalk
EdenGottlieb said:
Have you installed any background-running apps that may cause this problem? I don't know what can cause screen stuttering like you have. Have you thought about installing CM? It works great and is 1000 times faster than stock
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yes i have thought about it......but id need an idiots guide as ive never done that before...
Also im sure ive read 4.4 ota is coming soon , so i was going to hang on for it....
Is there a guide out of interest?
There are only guides for root and recovery, CM is only wiping and flashing. I will post links when I get home (although I'm pretty sure you can find them yourself in the All things guide thread, I recommend TWRP)
The OTA 4.4 update is very far away, march at least (I have my sources)
Sent from my iPhone using Tapatalk
EdenGottlieb said:
There are only guides for root and recovery, CM is only wiping and flashing. I will post links when I get home (although I'm pretty sure you can find them yourself in the All things guide thread, I recommend TWRP)
The OTA 4.4 update is very far away, march at least (I have my sources)
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
No problem......yes i can research.....thanks for replying
Try enabling the developer options (you dont need root and a howto can be found on google) and turn off all the transitions and see if your lag goes away.
Just giving this a bump
LBJM i hadnt seen your reply , so i will give it a try when i get home..
I flashed CM11 onto my Gpad but i didnt like it ( personal preference) ive now got the latest Mahdi Rom which is very much like the Nexus5 that i was wanting.
but still i get this lag in Lanscape mode when im scrolling up and down....one side lags to give a wobble effect.
wantefc said:
but still i get this lag in Lanscape mode when im scrolling up and down....one side lags to give a wobble effect.
Click to expand...
Click to collapse
In all apps or only in some? I see a stutter in certain apps that do not cache things far enough ahead (i.e. twitter) when I have the client configured to show the twitpics. However once I know everything is loaded I can scroll up and down without any stuttering problem. Some browsers also have this problem since they also only seem to load in memory the stuff that is rendered on the screen...
Based on what you describe I'm not certain that your wobble and my stutter are the same thing though...
Bump
Ive just gone back to Stock LG for the KitKat update and i still get the scrolling wobble effect in landscape.
Its not a deal breaker but it just bugs me....im suprised no one else has seen this.
its noticable in netflix when you scroll quickly
this is what i mean
http://forum.xda-developers.com/showthread.php?t=2486335
there is a youtube link on this forum demonstrating it.
bump......no one else noticed this?