[HELP] Loss of response on G2 screen !?!? - G2 Q&A, Help & Troubleshooting

I have been experiencing unresponsive spots on my screen. For example, in portrait mode, in Titanium Backup, I am unable to get Wipe Data button to work BUT both the Delete & Uninstall buttons, above & below it, will trigger instead. I have also experienced this happening in the Play Store where the Uninstall button will not respond. It seems to be happening in roughly the same area on my screen.
This just started happening recently & I would like to know if this is a known issue or what ?!
I am running the latest Mahdi ROM 7/9 with dr87's stock kernel on my VS980. I have since tried going back to the 7/7 build as well as trying Render & barts modded Dori kernel.
Please reply via PM if possible, many thanks !
*** I have been trying the 'Show Touches' Development Tool and it (obviously) still happens but it is showing touches in the area that is in question. IDK what this proves > not a hardware issue ?! Help .... please.

Related

[Q] Help with CarbonRom/TWRP/RazrM?

Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
mrnathanman said:
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
Click to expand...
Click to collapse
see post #7 here: http://forum.xda-developers.com/showthread.php?t=2355676
this should probably be in the Q&A/Help/Troubleshooting section....
Thank You So Much!!!!!!!!!!!!!!!!!
I know its soon and I am still crossing my fingers, but thank you!

[Q] Android 4.4.2 Kitkat ISSUES

I received the OTA for 4.4.2 yesterday after I had installed 4.4.1 manually. I noticed with both that the screen began to flash black quickly, and then went back to normal, every now and again. I noticed it the most in Hangouts, and for some reason the Play Store keeps opening at random...very annoying because it doesn't even load to show me all the new things, it just stays white. Is anybody else having this issue? I assumed 4.4.2 was to fix the screen flash but nope. Also I noticed GPS doesn't lock on unless High Accuracy is selected under the GPS settings, haven't gotten it to work otherwise with Mobile Data or Wi-Fi
Hi, I had a very similar problem in the past, while updating my Nexus 4 from 4.2 to 4.3. The solution is to clear cache.
1. Put the phone in airplane mode.
2. Go to Settings -> Storage
3. Find the second bottom most item, "Cached data," and touch it. It will ask if you want to clear cache. OK it and power down the phone.
4. Reboot and get out of the airplane mode.
This should fix it. You can alternatively clear cache from the stock recovery. If this doesn't solve it and the screen flickering persists, give Google a call.
GPS-Fix
Wink GPS-Fix
Hi there guys,
I have had the same problem updating from 4.4.1 to 4.4.2 and was looking for this fix,
here are the files that I used but I don't know for sure if it will work for you but for me it did the trick.
You have to try each one of them, for me the second one worked out, the first one didn't even flash on my phone.
So I guess you guys can give it a try.
After flashing and clearing (((Cache and Delvik/Cache)))) please reboot.
When I did the GPS fix worked right away, so it was a very quick fix based on a Galaxy S3 script and the best part was that
I didn't need to go back to a stock room or anything.
PLEASE IF THIS WORKS FOR YOU JUST HIT THANKS.
I'm not good at this guys so here are the two links the website give me if you like let me know if anything is wrong
I will send you guys the file directly.
(((((((((((( I DO NOT CLAIM ANY PROPERTY ON THIS FILES. THEY WERE ENTIRELY CREATED BY SOMEONE ELSE. )))))))))))))
https://anonfiles.com/file/0ec77a872...98258e69e265a9
https://anonfiles.com/file/0ec77a872...98258e69e265a9

[Q] (Q) Screen stays on when I miss phone call or msg

Hello.
I posted the question in the Q & A thread but I fear my question got lost in between the many that are asked.
I own a rooted S4 from Rogers Canada, which used to be on Alpha Infamous rom, an old version like the 5.0 from at least 6 months ago. Everything runned fine until recently. The phone started giving me some trouble. After missing a phone call while I didn't had the phone on me, the screen stayed on showing missed call until I happened to see the phone and pressing power to close it. The same started happening with message at about the same time.
Since I thought I might have installed a dumb apk on gplay that messed something in the settings, I went to get a new Rom. Alpha having no development for a long time, I thought I'd try something else.
I have tried both omega v25 and [23/03][4.4.2][XXUFNBH]< Echoe v18 > [07/02][4.3][NA4]< Echoe v12.1 "The Final Bean">, the latest which I run at the moment. Both gave me the same trouble with the screen staying powered after missing a msg or a phone call.
Since I don't know how to fix it, I was wondering if anyone could help me out ?
I'm no pro at rooting/flashing but I did the wipe dalvik, cache and everything before flashing both of the new rom. I didn't update the bootloader as I didn't remember clearly how or if it was necessary but the rom in general runs great so I figured out it was ok this way. The only trouble I have is with the screen as previously stated. I didn't flashed the modem either as I seem to have great download speed (without testing, simply feeling it).
So as of now, I'm running Echoe V18 with most of the bloatware disabled in aroma installer.
What can I do to fix this? I've tried googling but nothing close to my trouble came as result. Neither could I find an answer here, there's so many result I might have simply missed it.
Thanks for the help!
Laethageal
Anyone's able to help out ? My question is getting phased out but still has no answer. Please ?

Screen flashing off and on randomly after screen change

Hi everyone! I have a hardware related issue here.
I have replaced the screen (+digitizer in a whole) and since then it is randomly going off and on. Interestingly it even did the same in recovery (TWRP 2.3) BUT not with every software! Installing the TWRP 2.6 or above stopped it happening in the recovery.
I have tried various ROMs so far. The Eclipse ver3 did not flicker, but it has a problem with the registering on a network here in the UK. Stock + stock based ROM (Rage 1.2) are also switching on-off. I am currently looking for a working ROM.
Please let me know if someone with the same problem can find one.
Also tried to play with developer options like Disable HW overlays or Force GPU rendering with no effect.
I wonder if it is a different hardware version of the replacement screen or what else can it be? (screen came from etradesupply)
Update - problem solved
Good news. Installing CyanogenMOD 11 solved the screen flashing issues and everything seems to work right. Thank you developers!

Help with modems, proximity sensor, camera and auto rotation

Hi
I got a G2 (D802) the other day and so naturally I rooted and installed the latest CM nightly.
I didn't flash any new modems or kernels or anything like that, all I flashed was the ROM, GApps, Xposed binary and SU binary.
I've come across a couple of issues that I'd be really grateful if somebody could help me with!
1) If I use an app that accesses the camera and then exit the app, the camera will no longer work until I perfom a full reboot.
2) Every sensor that shows up in this app is showing readouts of 0 despite me moving the device around, shaking it, waving my hand over it etc. This results in me not being able to use auto-rotation, accidentally hanging up on calls because the screen doesn't turn off, not being able to play games that rely on the accelerometer and many other issues.
I keep seeing posts saying I should flash a different modem but I'm really not sure which one to use! There's about 4 different ones for the D802 and I don't want to brick my new phone by flashing the wrong modem!
All help is really appreciated! Thank you!!
BUMP! help needed!

Categories

Resources