My touch screen seems to work fine on 4.2.2 (specifically the rom at: http://forum.xda-developers.com/showthread.php?t=2719411) but when I flash a 4.4.2 rom, it does not seem to track my finger well. Half way through a swipe it will just stop reacting to my finger, and no matter how hard I press or move it around it will not detect my finger again until I lift it and place it again.
This is very bothersome as it makes the tablet almost unusable. Any help is very appreciated.
This is ANY 4.4.2, stock based, or AOSP I have tried multiple roms from aosp, and ive tried both the A and B roms at http://forum.xda-developers.com/showthread.php?t=2707363
Update
So I went back to a 10a 4.2.2 base stock. Like usual the touch screen behaved normally here, Then I flashed the latest Mahdi and it once again stopped tracking my finger.
I then flashed the discontinued dyn kernel (gpeish works too) and it started tracking normally. I wanted to use the AIC kernel for AOSP, but unfortunately it does not correct the issue. So what I did was, flash dyn to get it working correctly, then flashed AIC over top of that. It seemed to do the trick. I don't have the issue now. Though I am not sure what this means, or if other people have this problem.
zetorung said:
So I went back to a 10a 4.2.2 base stock. Like usual the touch screen behaved normally here, Then I flashed the latest Mahdi and it once again stopped tracking my finger.
I then flashed the discontinued dyn kernel (gpeish works too) and it started tracking normally. I wanted to use the AIC kernel for AOSP, but unfortunately it does not correct the issue. So what I did was, flash dyn to get it working correctly, then flashed AIC over top of that. It seemed to do the trick. I don't have the issue now. Though I am not sure what this means, or if other people have this problem.
Click to expand...
Click to collapse
Thank you so much, I thought that I got a defective PAD, I have
I know that this is a veeery old post, so to clarify and be sure about what you did
Flashed stock 10a 4.2.2
Flashed DYN Kernel
Flashed AIC
Have you figured out any way to resolve the issue with 4.4.2?
thank you
Orochikun said:
Thank you so much, I thought that I got a defective PAD, I have
I know that this is a veeery old post, so to clarify and be sure about what you did
Flashed stock 10a 4.2.2
Flashed DYN Kernel
Flashed AIC
Have you figured out any way to resolve the issue with 4.4.2?
thank you
Click to expand...
Click to collapse
Unfortunately no. I ended up selling it after a year or so to buy a nexus 9. Sorry I cant be of more help.
zetorung said:
Unfortunately no. I ended up selling it after a year or so to buy a nexus 9. Sorry I cant be of more help.
Click to expand...
Click to collapse
Thank you for the reply
Well I just keep flashing till it works like it should lol
I have the same issue ! For a moment there I thought the G Pad had a non-sensitive area like the iPads have xD
The strange thing is, this problem also appears on Lollipop roms...
Is there any solution available? Still having this issue with AOSP 6...
Related
Hey guys I have white galaxy nexus maguro.
The problem I facing is quite strange and I want help.
I have been using my phone from more than 6 months my phone works fine with stock rom i tried installing rom before months back a custom rom and it was CM 10.1 my phone touch starts to respond after sometimes clicks are happening everywhere i changed rom back to stock and problem goes.
So now after many months i came to know about this amazing rom for gnexus CrDroid based on Cm10.2
I just installed it and the problem i faced before is here again.
So conclusion to all this is my screen touch response is extra sensitive or i dont know what happens with it when i install a custom rom on it,
On stock rom its fine,
So what you guys think i should do or anyone else had the problem like that if they solved it please help thanks
Nuke_- said:
Hey guys I have white galaxy nexus maguro.
The problem I facing is quite strange and I want help.
I have been using my phone from more than 6 months my phone works fine with stock rom i tried installing rom before months back a custom rom and it was CM 10.1 my phone touch starts to respond after sometimes clicks are happening everywhere i changed rom back to stock and problem goes.
So now after many months i came to know about this amazing rom for gnexus CrDroid based on Cm10.2
I just installed it and the problem i faced before is here again.
So conclusion to all this is my screen touch response is extra sensitive or i dont know what happens with it when i install a custom rom on it,
On stock rom its fine,
So what you guys think i should do or anyone else had the problem like that if they solved it please help thanks
Click to expand...
Click to collapse
You didn't do anything wrong while flashing? Or maybe a mod? Maybe even an app? You could try to flash the ROM and don't install apps and see how that goes for some days. If that doesnt work maybe you could flash stock via fastboot and then flash the ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You didn't do anything wrong while flashing? Or maybe a mod? Maybe even an app? You could try to flash the ROM and don't install apps and see how that goes for some days. If that doesnt work maybe you could flash stock via fastboot and then flash the ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for replying
No I didn't do anything wrong its not my first andriod phone even tho that post was first one on xda never ran into problem.
I think its problem with gnexus many people have different issues with roms but mine is just that its giving me issues on custom roms tried many things flashing again dirty flashed everything.
on stock problem is gone but on the ones i mentioned i am getting this bug that i cant even use my phone i unlock it and touch starts to respond all over the screen
Hey guys since i am testing i just installed slimbean and its working perfectly just like how stock behaves so can someone tell me what slimbean 4.3 and Stock 4.3 have in common and what CM10.2 has not and giving me issues?
Ok so ever since I updated to any of the 4.4.2 rom (i.e. Cm11, Cyanfox, SlimKat and Carbon Rom) my accelerometer won't work correctly.
At first I thought it was a GPS issue but after looking into it more the GPS locks fine. It's only the direct in google maps or any other GPS like app that is messed up. For instance, when I'm using google maps and I'm facing north it will show me facing east, then when I change directions it can't figure out which direction I'm facing and spins around in circles and maps will crash. Same thing happens when I use GPS Status, the app will say I'm facing the wrong direction and when I move direction it starts to spin out of control.
I defiantly don't think its a hardware issue since everything was working fine with the touchwiz rom and 4.3 roms. If anyone has any clue on how to fix this I would greatly appreciate it. This is pretty much the only thing that is wrong for me with any kitkat roms.
I have a tmobile galaxy s3 and current running SlimKat build 3. :crying:
Try FasterFix app
Perseus71 said:
Try FasterFix app
Click to expand...
Click to collapse
I gave it a shot but no luck. I have also used GPS status and FasterGPS but like I said before I don't think its a GPS issue because it does lock on to my location fine. It's just my compass doesn't work correctly.
I believe CM has a Advanced Option to Re-Calibrate Accelarometer. Settings > Advanced is where the option is I think. I use Slim Bean so I don't have CM details.
Oh yeah I forgot about that but it still didn't work. I appreciate all the ideas though.
You may want to go back to Stock and then try. Just to rule out any hardware issues. It will also wipe any corrupt firmware.
Perseus71 said:
You may want to go back to Stock and then try. Just to rule out any hardware issues. It will also wipe any corrupt firmware.
Click to expand...
Click to collapse
Do you mean odin to stock or just flash a stock rom? If it's odin I'll definitely try it when I get home. The thing I find weird is that when I flashed the S3Rx rom, everything was working fine.
I'd do Odin before trying anything else.
So I odin back to stock and like before everything was working properly. Then when I flashed back to carbon rom, is back to pointing in the wrong direction and spinning out of control.
I'm surprised that I'm one of the only if not the only one with this problem. Is there an app that I can manually calibrate which direction I'm pointing?
I'm out of ideas...
Can you flash a different kernel on top of Carbon ?
Perseus71 said:
Can you flash a different kernel on top of Carbon ?
Click to expand...
Click to collapse
I flashed KT kernel, BMS, Harkness and DKP. For a little while it seemed like BMS had fixed it but then went back to the same ol' sad story. :crying:
Try Another Rom please. Not just Carbon. This time try a 4.3 rather than Kitkat.
I have tried other roms and I stated that this didn't happen till I started using Kitkat roms. When I was on carbon 4.3.1 there weren't any problems as well as on S3Rx 4.3 rom. Not sure why this only happens on Kitkat roms and what seems like only to me. I'll continue to look for solutions cause I really like the look and feel of Kitkat.
So after searching and searching I finally found a fix! I was about to give up hope but decided to try one last kernel, Quantum kernel. At first it seemed like it wasn't working but I had to calibrate my accelerometer with GPS Status. After that everything was gravy! I hope this helps others that have the same problem I did!
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
I'd try using the latest wild kernel.
g0at1 said:
I'd try using the latest wild kernel.
Click to expand...
Click to collapse
well i think i did try wild kernel with cm12.1 latest nightlies. The issue gotten worse. More random reboot occured.
Currently on slimLP with his zerkernel v1.7. I thought this one is perfect, but then out of nowhere the random reboot occured again. It's not as frequent as before but still happen.
Right now I'm using Mokee with wild kernel and everything is going well.
Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
hawkwind212 said:
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, i think the issue are only on cyanogen based ROM. When i use the lolipop such as Super Mini V6.5 by henrypham91 and lgviet team, it's all good. Deep sleep normaly, no sound delay when game on 2D graphics, and all. But then again, it's noticeably slower if you compare against CM head to head. I really love CM or AOSP based rom because they are so fast.
g0at1 said:
Right now I'm using Mokee with wild kernel and everything is going well.
Click to expand...
Click to collapse
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Oyongx said:
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Click to expand...
Click to collapse
Mokee is a Chinese CM based rom.
g0at1 said:
Mokee is a Chinese CM based rom.
Click to expand...
Click to collapse
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Oyongx said:
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Click to expand...
Click to collapse
Their website has an English version. There should be a British flag on the upper right side. Then download their history zip which is a kind of final release.
It used to work but just noticed today it isn't any more. GPS will still find me, but it won't travel along with me in google maps and none of the satellites lock on using GPS toolbox. It shows 20 or more satellites available but none lock. If I do a search for nearby places it gets it right every time but it won't lock on to any satellites. I am rooted, I tried changing the rom and even loading a fully stock one and it still isn't working. I don't get how some of this stuff will work but I can't get any full lock.
Is this likely a device issue or something that I can fix?
I am also having this issue with my Pixel (non XL). Next weekend I will try and reset the device but I have had this issue for a few months now. I am not sure if it's software or a hardware problem.
JAYNO20 said:
It used to work but just noticed today it isn't any more. GPS will still find me, but it won't travel along with me in google maps and none of the satellites lock on using GPS toolbox. It shows 20 or more satellites available but none lock. If I do a search for nearby places it gets it right every time but it won't lock on to any satellites. I am rooted, I tried changing the rom and even loading a fully stock one and it still isn't working. I don't get how some of this stuff will work but I can't get any full lock.
Is this likely a device issue or something that I can fix?
Click to expand...
Click to collapse
Did you change kernels as well.
Way back in the day I had an issue like you described and the only way to resolve was to restore backup in which gps worked.
Then fire up phone confirm GPS lock. Then do all the flashing.
The only solution I ever knew to this issue was to restore a backup or start over from factory images.
parakleet said:
Did you change kernels as well.
Way back in the day I had an issue like you described and the only way to resolve was to restore backup in which gps worked.
Then fire up phone confirm GPS lock. Then do all the flashing.
The only solution I ever knew to this issue was to restore a backup or start over from factory images.
Click to expand...
Click to collapse
Yeah I changed the kernel. I tried completely unrooting and flashing a fully stock roms (March and April ROM) then reflashing the rooted rom I'm on (pure nexus) and even a non stock kernel (ElementalX) and it still won't lock.
JAYNO20 said:
Yeah I changed the kernel. I tried completely unrooting and flashing a fully stock roms (March and April ROM) then reflashing the rooted rom I'm on (pure nexus) and even a non stock kernel (ElementalX) and it still won't lock.
Click to expand...
Click to collapse
I assuming no back up then if you didnt restore that.
In my experience i dont recall flashing the stock rom alone enough to undo the change to the kernel that screwed up GPS.
It wouldnt lock on stock rom?
try flashing stock kernel by itself maybe?
parakleet said:
I assuming no back up then if you didnt restore that.
In my experience i dont recall flashing the stock rom alone enough to undo the change to the kernel that screwed up GPS.
It wouldnt lock on stock rom?
try flashing stock kernel by itself maybe?
Click to expand...
Click to collapse
Hey,
Flashing stock firmware actually includes the stock Kernel by the way. :good:
Cheers...
It didn't lock on any of the stock roms I flashed (which as user 5.1 stated included the stock kernel) but it used to work fine before on stock roms and even on pure nexus at one time. Not sure what happened or why it just stopped locking onto satellites.
JAYNO20 said:
It didn't lock on any of the stock roms I flashed (which as user 5.1 stated included the stock kernel) but it used to work fine before on stock roms and even on pure nexus at one time. Not sure what happened or why it just stopped locking onto satellites.
Click to expand...
Click to collapse
Hey,
I don't think it will fix it, since several ROMs didn't... But did you try reverting to an older version which used to work. You likely did it already. Just in case you didn't...
Otherwise you may try contacting Google or whom you bought your device, report your issue and see if they are already aware of the situation with others users maybe? As it sounds like a hardware issue...
Looks like you are far of being alone here: https://www.google.fr/search?q=goog...j0l2.8956j0j4&sourceid=chrome-mobile&ie=UTF-8
Good luck...
5.1 said:
Hey,
I don't think it will fix it, since several ROMs didn't... But did you try reverting to an older version which used to work. You likely did it already. Just in case you didn't...
Otherwise you may try contacting Google or whom you bought your device, report your issue and see if they are already aware of the situation with others users maybe? As it sounds like a hardware issue...
Looks like you are far of being alone here: https://www.google.fr/search?q=goog...j0l2.8956j0j4&sourceid=chrome-mobile&ie=UTF-8
Good luck...
Click to expand...
Click to collapse
Yup I did try that already. I am ordering a replacement tonight.