Database Info

[Q] Problems with touchscreen do I have to send it in

I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?

qaaqq said:
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
Click to expand...
Click to collapse
I have the same issue, only the position is different. Have you worked out a solution? Or still waiting for it? Anyone?
Im on Miui with matrix cfs 5.5 (9023)

huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine

bucimaci said:
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
Click to expand...
Click to collapse
I have this problem also, im on CM7 nightly. cant unlock the screen. Phones barely 3 days old

Had that same problem, and it's gone now. Don't know what did fix it, but I flashed new radio and Trinity kernel, and the problem is gone now...

I thought with the 2.3.5 the problem was solved, but its back now... dunno what it is, my phone is 2 weeks old.

I'm experiencing the same issue on a stock, not rooted or in any way modified Nexus S I9023 (SCLCD version) with Android 2.3.6
Also the settings button is right under the line (so the location is different from the video) and it is unresponsive as well.
Does anybody have any idea what to do about this???

[Resolved] [Q] All sensors on LG G2 not working!

So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
UPDATE: Thanks for all who helped! I just found out i was using a damaged kk modem with no rotation. :/

Yulianstefanov said:
So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
Click to expand...
Click to collapse
Sounds like a hardware issue. I would send it in for repair. Even though you voided your warranty when you flashed a rom.

zelendel said:
Sounds like a hardware issue. I would send it in for repair. Even though you voided your warranty when you flashed a rom.
Click to expand...
Click to collapse
I just dont get it, it never fell and it has a cover. i just don't see why they don't work... Anyway i guess i'll have to send it to repair.

Yulianstefanov said:
I just dont get it, it never fell and it has a cover. i just don't see why they don't work... Anyway i guess i'll have to send it to repair.
Click to expand...
Click to collapse
Is there any way it could be a software issue?

If it did it on stock then it is most likely a hardware issue.
Just because you didn't drop it doesn't mean the hardware hasn't failed.

Yulianstefanov said:
So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
Click to expand...
Click to collapse
Its a long shot, but try 're-flashing the modem file. Some of the sensors won't work if you have the wrong one installed, maybe part of your is just broken and need to be restored.
There is a thread in the g2 forum with the modem files, I remember getting mine there.
Maybe you will be lucky and that will fix it.

I think you should go to a Repair Service. But before go to repair service, you should try some ways!
1.Flash FULL STOCK ROM(Not part of stockrom!)
2.Just leave it for 1 days.
3. If there are some manufacture settings, please enter that setting, and check for sensor.(Like Korean SHV-E120 Number of manufacture setting is 319712358) you should find settings from google.

Jason Hyunwoo said:
I think you should go to a Repair Service. But before go to repair service, you should try some ways!
1.Flash FULL STOCK ROM(Not part of stockrom!)
2.Just leave it for 1 days.
3. If there are some manufacture settings, please enter that setting, and check for sensor.(Like Korean SHV-E120 Number of manufacture setting is 319712358) you should find settings from google.
Click to expand...
Click to collapse
Thank you so much , i restored back to full stock rom , messed around in the sensor settings and after a reboot everythings fine. THANKS!

bweN diorD said:
Its a long shot, but try 're-flashing the modem file. Some of the sensors won't work if you have the wrong one installed, maybe part of your is just broken and need to be restored.
There is a thread in the g2 forum with the modem files, I remember getting mine there.
Maybe you will be lucky and that will fix it.
Click to expand...
Click to collapse
Thanks but i saw your post a bit late and i restored to my stock rom already, but if i go back to mahdi ill definately try it. THANK YOU

Proximity

Alright I'm asking to see if anyone else has had same issue..... My proxinty sensor hasn't worked ever since I flashed cm12 and even after restoring back to stock backups. I have to install disable proximity sensor module to be able to turn screen on and off while in a call. I never had a issue with it until I flashed lollipop and now no matter what I do its a no go... I'm thinking it either completely went out or maybe I need to flashtool back to kk to get it back ... Has anyone else had similar issues?
2SHAYNEZ

Ambient display keeps screen backlight on

Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.

Yeah same happened with cm 12.1 latest nightly too.....just checked it now...

The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .

therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.

therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??

Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks

therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.

Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display

therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.

Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .

therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!

FP hardware not available!

Hey guys! I have a problem with my P2, some times I get fp hardware not available! A lot of times it works again after activating/deactivating developer mode and restarting the system! I'm on LOS 14.1 but I tried AEX and Havoc too

Funny, i'm getting the same thing. I'll try the developer mode trick.

same here
same happened to me i am on stock rom. some days back i was on aosp extended and everything was fine. and yesterday i got this problem "fb hardware not available' i tried factory reset n flashed los 15 but it didnt help now back on stock but fp still jot working

I lost it on stock s251.. only gestures were working in Safe mode. Tried los 15 with the fpgesturesfix zip .. i only could use fp sensor once. But it stopped the next morning. Any fix? Going back to stock (7.0 /6.0) will help?

Developer mode trick didn't work for me, so i switched from RR to CRDroid, but no joy. Maybe something wrong with oreo sources, maybe stock fixes it... Maybe, maybe...

Seems that it's working now for me..I just did a full wipe, with internal storage too, and than flashed back Los 14.1, then I activated developer mode and restarted the system...it's working until now..

Well, my fp sensor also came back after doing precisely nothing just started working again. Weird.

Flash these files , according to your rom base, after flashing rom. Works for me. ?

on stock
suvam69 said:
Flash these files , according to your rom base, after flashing rom. Works for me.
Click to expand...
Click to collapse
i am on stock s251. which fix to use??

Lavesh05 said:
i am on stock s251. which fix to use??
Click to expand...
Click to collapse
I was on stock and my fp was faulty. I am not sure but u can try the Aosp fix. Don't blame me if your phone blows up as I use these files with custom roms.