Related
I think there is something wrong with my digitizer. I'll be using the phone and the screen will act as if its being continuesly pressed somewhere else so it won't scroll and I can't hit icons until I turn it off and on again. Not soft reset. It happens almost everything time I use it. It has happened several times while writing this. Any ideas? Something under digitizer?
Sent from my HTC Liberty using XDA App
slowjett said:
I think there is something wrong with my digitizer. I'll be using the phone and the screen will act as if its being continuesly pressed somewhere else so it won't scroll and I can't hit icons until I turn it off and on again. Not soft reset. It happens almost everything time I use it. It has happened several times while writing this. Any ideas? Something under digitizer?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Take it back!
Not an option. I bought it privately.
Sent from my HTC Liberty using XDA App
slowjett said:
I think there is something wrong with my digitizer. I'll be using the phone and the screen will act as if its being continuesly pressed somewhere else so it won't scroll and I can't hit icons until I turn it off and on again. Not soft reset. It happens almost everything time I use it. It has happened several times while writing this. Any ideas? Something under digitizer?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
OK, so you bought it privately and returning is not an option, so how about some more information. Has the phone been rooted? What ROM are you running? Have you tried a full wipe to see if that solves the problem?
I have had the phone for a couple months it just started doing this. I'm running liberated fr007. Rooted. Have not tried hard reset.
Sent from my HTC Liberty using XDA App
I thing I'm having the same problem.
My touchscreen get crazy completely randomly, sometimes I'm typing an sms and its almost imposible to write, cause it just get stuck even on the "P" letter or on the emoticons thing of the keyboard.
Sometimes I just can't switch between my homescreens (its like the thing refuses to work), what I do is switch off and on the screen (the slide to unlock works, but not the homescreens) and after several attempts it comes back to normal.
But it all started when I installed the latest version (6.1.1) of CyanogenMod.
Did anyone get a solution?
I don't want to roll back to a previous version or try another ROM.
Thanks!
Try to fix superuser permissions idk id probably just try to reinstall after clean swipe and restore everything with my backup pro. Also check the temp of the phone high temps around 100 mess up the touchscreen responding.
Signatures are fancy.
sorry... but im kind of a noob
How do I check the permisions?
What should I look for?
Thanks!
SergioCR said:
Did anyone get a solution?
I don't want to roll back to a previous version or try another ROM.
Click to expand...
Click to collapse
i would try doing a complete wipe and installing it again. if you've been using your phone with no errors previously, then the issues shouldn't be with your hardware but perhaps with a bad install of the current rom.
mattbollenbach said:
i would try doing a complete wipe and installing it again. if you've been using your phone with no errors previously, then the issues shouldn't be with your hardware but perhaps with a bad install of the current rom.
Click to expand...
Click to collapse
I've done that before.
But it looks like there's a new nightly version of CM... I'll give it a shot, hopefully this is gonna fix it
SergioCR said:
I've done that before.
But it looks like there's a new nightly version of CM... I'll give it a shot, hopefully this is gonna fix it
Click to expand...
Click to collapse
would love to know your outcome on this - as it is happening on my phone as well
running a FR008 - was running perfectly until early this morning - then the same behavior that you were getting.
I cant get the keyboard dock to stop changing the tablet volume. Often times when I touch the keys it pulls up the volume changing menu!!!! It is making me mad and I don't know why.
Im running stock everything for now fyi.
Sent from my Transformer TF101 using XDA Premium App
Has anyone else experienced this? I just bought this dock, and it flashes up the volume control CONSTANTLY. It happens basically any time I use the keyboard, or touchpad, or even touch the tablet screen. It makes the keyboard totally unusable.
I originally had AOKP v1.5 as a ROM, and figured it was some incompatibility that made it keep doing that, so I flashed a rooted Stock ICS rom, and it still happens!
I'm becoming semi-convinced that it's a hardware problem, and I have a faulty dock... I'm gonna try wiping data and cache and going back to this same rom, and see if this same stuff happens with no other apps installed.
Has anyone experienced this, other than the above poster? Google searches and XDA searches bring up nothing but this one post...
Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.
bigb252 said:
Hey everyone, I woke up this morning to find a surprise! My Atrix screen was unresponsive. It took me a couple reboots to figure out that the top part of the screen doesn't respond to touch. Worse yet, none of the capacitive buttons work. So if I get into an app, most of the time, there's no real way for me to get out of it, thus requiring a reboot and more careful selections.
The weird part is, it happened within a span of about 2 hours. I woke up around 5:30AM, checked some emails and texts, and woke back up around 7AM with a buggy screen. It did drop from about 18 inches off the couch last night. But everything was in working order...
Right now I'm in the process of backing up my text messages, because I might have to use a set of them to prove my case in court.
What's the first steps to try to get it back working? Or do you think its a hardware problem(maybe a cable loose)? As far as returning it under warranty goes, I'm rooted and unlocked on Kenn's GB ROM, so that's a no-go.
Click to expand...
Click to collapse
you are unlocked/rooted/custom rom = no warranty
anyways backup and maybe reflash the rom and see how that goes.
Hopefully you don't need to replace the digitizer... But if you do, there are lots of videos and it's reported to be one of the easier phones to do. Keep that in your back pocket as an alternative to a lengthy and costly court fight over a phone with no warranty!
Sent
Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.
Bump...
Still lost
I would suggest backup all you apps and do a complete wipe of data. I had a similar problem when I first installed Alien. This fixed the issue.
bigb252 said:
Thanks guys, I already knew the risks associated with rooting and unlocking. I used an app called SMS Backup+ that allowed me to backup all my sms/mms and it also linked and sent copies to my Gmail.
I'll go ahead and try a reflash
*EDIT*
Did a quick wipe of the phone, and during setup, everything was OK! When blur came back, it was back to the same thing.
Click to expand...
Click to collapse
I would do a wipe and reinstall. You could also fix your permissions through rom manager or cwm.
Sent from my MB860 using XDA Premium App
I had a simillar problem: WIPE through CWM solved this problem
hi, guys i had the same problem... I remember getting it shortly after updating it to the leak version of gingerbread. Since then I have flash Alien built #3 but the problem remains...
I'm currently doing a Nandroid backup of my phone so i could try flashing to cherrypie hopefully this will solve my problem cuz I'm seriously feed up with it...
do you guy's think this will help? if so any suggestions before i flash? thanks in advance...
I had this problem brand new out of the box. I just took it to the store and they gave me a new one. One other thing i noticed was the FP sensor/button was almost like loose and i had to push it in real far for it to work. Maybe its a stuck FP button...
Sent from my MB860 using XDA App
im having the same issue, i cant make the buttons work, i have wiped everything in CWM, and using fastboot also and nothing, also tried flashing different roms but the problem persists, if anyone know how to solve will be great
thanks
I think you have one file corrupted... I'll try to remember which
Sent from my MB860 using XDA App
I think it may be touchpad.cfg. try Googling that and see if you can find a clue.
Sent from my MB860 using XDA App
Try here: http://www.kandroid.org/online-pdk/guide/keymaps_keyboard_input.html#androidKeymapKeyLayoutMapTitle
Sent from my MB860 using XDA App
thnaks for the answear, i flashed the 10 point multitouch patch to see if solved the problem but it didnt, yesterday i reproduced the error but idk how to solve ir, im gonna make a thread to show what i did
So I've tried everything I could think of. Reflashing ROM, using a different ROM, different browser, everything minus a different modem, which I'm not sure would really do anything. But where I'm at is that anytime I go to status on facebook it closes the browser back to the home. I'm on Frozen ROM at the moment, I've tried on stock, same issue. Tried on the ASOP ROM, same issue, tried on those ROM's with Dolphin, Miren, Firefox, Stock Browser, all the same issues.
So will a modem actually make a difference is how the phone handles? Or is it more related to data speeds? I don't know what else to do, this is driving me absoluetely nuts. Thanks Guys.
Try this go into settings / manage application / all application & wipe data from browser & wipe data from Google search then reboot if that doesn't work I don't know
Sent from my Nexus S 4G using xda premium
Figured I would move it to the proper area. Haha. I really appreciate all the help Bro. Tried the other route you said, nothing doing. So I don't know either. It's annoying though. I think I got the phone into a bootloop now tried to install a different ROM see if that would work, and doesn't seem to be working. Piece of crap. Just my luck. Ha.`
What kernals were/are you running?
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
odin back to stock
and clear out the sd card. redownload everything and rebackup.
Did you uninstall the Facebook app and redownload it? Wipe data in it before uninstalling. Did you try a different browser like Miren or Dolphin?
xTMFxOffshore said:
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
Click to expand...
Click to collapse
Well, you aren't running without a kernel - the kernel is the core of the Android operating system.
Maybe you're having a hardware issue, such as a touch screen that's acting up (you said it wasn't force closing or anything, right?) - it could be registering false touches in the wrong location... I'm just taking a shot in the dark on this one, since it sounds like you've tried restoring just about everything...
I would suggest reformatting your sd card (copy the contents to your computer first, the card WILL be erased).
Then, Odin a full stock tar (try DI18, you'll get an OTA to EC05 after you boot).
Then use the one click root and recovery - be sure to have the rom on your sd card, especially if you use an ext4 recovery like 3.1.0.1, because of the file system conversion (stock kernel won't boot ext4, so you'll need to flash the rom and an ext4 kernel before rebooting from recovery - Genocide or ACS's twilight zone or vision kernel... I would stick to Genocide for now, under worked the best for me)
You might want to skip the rooting step momentarily, so you can see if the same problem occurs on a completely stock setup.
Finally, I would suggest carefully cleaning your touch screen with something mild - I use eyeglass cleaner (safe for glasses with all the expensive protective coatings), other users here might have other suggestions.
This should cover all of your bases, and if you still have problems, it might be a hardware issue.
I do want to point out that (unless I'm missing something about what you're trying to do) the facebook that you access from the browser is loaded from their servers every time you connect - it isn't software on your phone. It cannot be the older version, not like an app, which has to be updated on your phone. The pandora issue sounds like a different issue, but I still need to test that (had to get to sleep last night, I was passing out mid-sentence, lol)
EDIT: re read the first post... Pandora issue was mentioned in the SRF thread... But it seems you did try stock and other roms...
When you say it closes back to home, I think I misunderstood - I had an issue once or twice where facebook would act up, going back to my facebook home page, but did you mean that the browser simply closes and dumps you back to your phone's home screen?
Because that could be as basic as your capacitive home button registering a false touch (the opposite of the unresponsive button issue we're all used to, lol)... But cleaning the touch surface could still help... Turn the phone off first, and apply whatever cleaner you use VERY lightly... Don't use household cleaners, if you don't have eyeglass cleaner then I would research whether rubbing alcohol is safe for gorilla glass...
Side note - swype suggested "guerilla" glass... made me chuckle...
Sent from my SPH-D700 using XDA App
What he said. ^... Also I would let it
Repartition and reset time when you Odin back to stock. I know most people say not to when flashing some things, but this would be an exception. Also when you flash to stock use the victory.pit file as well as the ROM tar.
Sent from my SPH-D700 using XDA App
All righty. I'm gonna try all that. As really nothing else has worked. I do think it's something with the screen though.....I just can't figure out why it only happens on the NEW facebook. I got her using the APP now she was only using the browser before, but I would punch say four letters it would bump a couple more then close. So you may be onto something with that touch screen registering incorrect keys so would that have anything to do with the contents of the SD card itself? Or is that an actual hardware conflict with the facebook (newer version) of the software? Cause it works fine on the APP. So I guess I'm basically at a loss for how this really makes any sense ,but really appreciate all the help from you guys.
Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.
If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.
DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads
Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.