[Q] [CM9][ICS] Help! Touchscreen issue, Kernel irrelevant - Galaxy S II Q&A, Help & Troubleshooting

1st Post: Current status(Top), Problem (End)
2nd Post: Fix (doesn't work in the newest Build)
----------------------------------------------------------------
The Problem is back with the new 02202012 Build:
kevuin said:
kevuin said:
Oddly enough the Problem with a unresponsive area on the touchscreen is back with this new build, even when I change the Touchscreen Sensitiveness in the new Setting menu. No matter which value (yes, even 10 which had worked before), the problem was there.
Even the old way through Terminal Emulator doesn't work anymore, i guess something has been changed there.
Help !
Click to expand...
Click to collapse
codeworkx said:
are you sure it's no hardware defect? mud or water on the display?
Click to expand...
Click to collapse
That's what I had thought at the beginning too, but it went away when i flashed Stock and also when I set it the sensitivity manually with Terminal Emulator (as written here)
It's unlikely that it's just a loose contact (a.k.a. Wackelkontakt) and that it only worked when I used the Fix/stock rom..
did you change anything else in the last build that could've affected this ?
Thanks for everything BTW !
Click to expand...
Click to collapse
codeworkx said:
we just added the sgs2 settings which allows to do the same you've done via terminal emulator.
does it only happen if charger/usb cable is connected? could be a broken cable.
Click to expand...
Click to collapse
kevuin said:
That's what I thought, i just tried 'cause you never know
It's definately not because of the charger (i know the problem with some certain inofficial charger where the touchscreen stops working when plugged in. but thats not it)
It's there all the time :/ I'd guess it's because of something else you might've changed in this build then.. any other ideas ?
Click to expand...
Click to collapse
----------------------------------------------------------------
The Problem itself + everything already discussed:
After I didn't get any more help in the General Discussion Thread, I had no choice than opening another.
Here my problem and help so far:
kevuin said:
Hey Guys,
after i found some lag/problems with my touchscreen (like no response at all) sometimes, and it always helps/goes away when i turn my screen off and then back on again.
But now (idk if it's because of this build, or my hardware) i have a whole horizontal stripe not getting any information about where my fingers are at any time. That "dead" area starts after the first few pixels from the bottom (where the homebutton etc. is) and is about 1cm wide (direction top), reaching from left to right of the screen.
It's about the whole "Slide to Unlock" area on iPhones.
I thought it was a Hardware problem of mine.. so i got rid of my yellow triangle, flashed some old Stock backup i had laying around and i noticed that the problem was totally gone! next to some laggyness everywhere the area i described was acting normal !
After that i went back to CM9 and the problem is back =/
Any ideas what i can do about it or what this is caused by ?
Thanks alot !
Click to expand...
Click to collapse
mudferret said:
^ re touch screen, its because of the lpb kernel; install lp6 kernel (cm9 one, not Chainfire)
Click to expand...
Click to collapse
kevuin said:
i just flashed the kernel and oddly enough the problem is still there ! =S
now what ?
Click to expand...
Click to collapse
Additionally to all of this, I managed that my phone worked normal again (on the 02172012 Build) after I deleted the market and reinstalled from some forum because it didn't work at all.
But the touchscreen problem was back after I rebooted and wiped all caches right after.
I wasn't able to replicate this fix ever since..
so now I know it's not a hardware problem (or maybe a loose contact? ..unlikely)
Picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas what I can do about this ?
Any help and Ideas are welcome !

Sadly enough, this fix doesn't help anymore in the latest build
---------------------------------------------------------------------
Thanks to the fast response of XpLoDWilD everything is fixed again !
XpLoDWilD said:
Can you please run this command in Terminal Emulator (or adb shell):
Code:
echo "10" > /sys/class/sec/sec_touchscreen/tsp_threshold
and tell me if it's better ?
Click to expand...
Click to collapse
Thank you so much!!!
EDIT: For anyone who doesn't undestand
go to Terminal Emulator and type:
Code:
su
echo "10" > /sys/class/sec/sec_touchscreen/tsp_threshold
and then reboot so changes can take effect
If you have problems with touch sensivity:
XpLoDWilD said:
Just raise the "10" value. Something around 30 is nice, default is 50.
Click to expand...
Click to collapse
alsgrigorjevs also made a video about this

kevuin said:
Thanks to the fast response of XpLoDWilD everything is fixed again !
Thank you so much!!!
Click to expand...
Click to collapse
i read the thread and i will post the XploDWilD's answer, i have read that 5 min ago lol

It turned out that my phone had a Hardware defect after all, I flashed Stock and got it repaired !

Related

"Connection problem or invalid MMI code" when typing in most # codes into the dialer?

"Connection problem or invalid MMI code" when typing in most # codes into the dialer?
Hi, anyone else experienced this when typing in a code such as #*06# or whatever into the dialer? It is annoying, what is wrong with my handset?
First of all it says USSD running and then "Connection problem or invalid MMI code" ?
Types in no problem for me a factory reset wipes all data might be the answer ,
jje
JJEgan said:
Types in no problem for me a factory reset wipes all data might be the answer ,
jje
Click to expand...
Click to collapse
Thanks for the reply, and yeah I have already done that, factory reset it... Maybe it is to do with when I flashed it or something? Is there a way I can get it back to pretty much factory condition - in terms of flashing it, etc (I am a complete noob so have no idea). Thanks
Just got the same message when I tried to add a couple of contacts to speeddial. Will check it out later.
B3311 said:
Just got the same message when I tried to add a couple of contacts to speeddial. Will check it out later.
Click to expand...
Click to collapse
Hi mate, thanks for the reply. At least someone else gets this with this same phone, not just me...
Okay, can you check that when you make a call does "conditional call forwarding active" come up? I have tried to disable that as it is annoying and even phone 3 mobile and they explained how to do it, yet still comes up. I have gone and reset my phone to factory settings yet it's still a probkem. I think the "Connection problem or invalid MMI code" and this must be linked, as I am sure I noticed both started at the same time?
dynamicbot said:
Thanks for the reply, and yeah I have already done that, factory reset it... Maybe it is to do with when I flashed it or something? Is there a way I can get it back to pretty much factory condition - in terms of flashing it, etc (I am a complete noob so have no idea). Thanks
Click to expand...
Click to collapse
Stock rom post in the dev section flash a stock rom should clean .
jje
JJEgan said:
Stock rom post in the dev section flash a stock rom should clean .
jje
Click to expand...
Click to collapse
Hi JJEgan, thanks for the advice. Is this fairly simple?
Is this the thread I want, and how do I do it (literally I only came on here in the first place because of the problem, I am in no way anywhere near a pro at these sorts of things)?
http://forum.xda-developers.com/showthread.php?t=1130625
Cheers.
Has anyone found a fix for this? On my phone it didn't work in Stock, didn't work when I flashed it to KF3 and a factory reset doesn't help either.
finally found a fix for this. You must use the stock Phone dialer to type in the code!!!
I've been using GO Dialers to type in the code, that's why its not working!! I am on Litening ROM 1.4. I thought those codes only work on stock rom, stock everything but that is not the case here.
Have fun everyone
ok dont know if it will work for you but it worked for me
add comma (,) in the end of the code
example:
*100*2# into *100*2#,
works for me
Heavens_King said:
ok dont know if it will work for you but it worked for me
add comma (,) in the end of the code
example:
*100*2# into *100*2#,
works for me
Click to expand...
Click to collapse
Does not work for me:/
Heavens_King said:
ok dont know if it will work for you but it worked for me
add comma (,) in the end of the code
example:
*100*2# into *100*2#,
works for me
Click to expand...
Click to collapse
where do you even get a comma in the dialer? mine doesn't.
adhistl surgical
poppienutshell said:
where do you even get a comma in the dialer? mine doesn't.
Click to expand...
Click to collapse
Any fix ?
Hello Every One I Have The Same Problem With My T-PAD
I Tried Every King Of Solution But Still Same Problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DELETE ME

Edit: Delete me
**********
Edit: Delete me
**********
Edit: Delete me
Good work for the beginning , normally chinese Rom working for international users . and You has been reworked on it.
eng_matt said:
Good work for the beginning , normally chinese Rom working for international users . and You has been reworked on it.
Click to expand...
Click to collapse
Thanks! I'm guessing that's Google Translate?
Excellent Work!!!
Meticulus said:
Thanks! I'm guessing that's Google Translate?
Click to expand...
Click to collapse
Meticulus, It's nice to see you more and more here at XDA, all you hard work is really appreciated.
Jesse6749 said:
Meticulus, It's nice to see you more and more here at XDA, all you hard work is really appreciated.
Click to expand...
Click to collapse
Thanks, I'm really enjoying it. I've always been interested in how sentence structure and grammer seems to be different in other languages, so that when it's translated, verbs and nouns look mixed up. Well at least from my perspective
Did you change or add samsung keyboard ?
eng_matt said:
Did you change or add samsung keyboard ?
Click to expand...
Click to collapse
I have noticed the issues with the default keyboard.... I'll put it on the list.... Thank you for pointing it out.
I'm a noob when it comes to using Odin, can someone instruct me on how to use it specifically for this? Thanks
just bought a GP5, about to root, looks like the only option here so i hope you stick around man! thanks!!!
Edit: well man my home button isnt working new kernel?
Edit2, market forclosing settings forclosing, keyboard is super funky (knoWn) ;-)
Reboot into clockwork mod and do a wipe/factory reset.
let me know how it goes...
Good Rom!!!
Meticulus said:
I have noticed the issues with the default keyboard.... I'll put it on the list.... Thank you for pointing it out.
Click to expand...
Click to collapse
I have been running the rom all day so far I have not had any issues and it is very smooth and fast. I did do a complete factory reset wipe 3 times with Clockworkmod Recovery before flashing this with Odin and so far it is working ok for me, I do use my own version of Swype keyboard instead of the default keyboard, maybe that is why I have not seen the keyboard issue.
Meticulus said:
Reboot into clockwork mod and do a wipe/factory reset.
let me know how it goes...
Click to expand...
Click to collapse
WOW. that worked man. thanks!! hope to see this thing develop with a blackout theme... ugh *drool*
Samsung Keyboard problem fixed.
@Meticulus , you can use my files for keyboard. problem fixed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samsung Keyboard problem fixed.
We are using now , lastest orijinal Swype Keyboard for samsung ;
use root explorer ;
copy all my files into the system folders with the same logic.
/system/app/Swype.apk
/system/lib/libSwypeCore.so
Now you can change keyboard ;
Setting ---> Language and Keyboard ---> Select input method ---> Swype.
Finish. That's all.
Download :
http://www.mediafire.com/?g93xo561hp4f5w6
or;
http://uploaded.to/file/9ahu9y32
Just posted R3 ... let me know what you think...
Based on ZCKPA? As a Chinese I'm really interested in the different between KPA and old ROM.
Verrrrrr Niccccccce
I just loaded it up and looks it so much better than the stock rom. So far no issues. Keep up the good work, I really like your boot animation.
Skip
edit: About 3 hours later, I just had a spontanious reboot as it was setting on my desk.
This would be great if it was available for Galaxy 5.0 international/Europe version any chance ? great work by the way.
SkipKelley said:
I just loaded it up and looks it so much better than the stock rom. So far no issues. Keep up the good work, I really like your boot animation.
Skip
edit: About 3 hours later, I just had a spontanious reboot as it was setting on my desk.
Click to expand...
Click to collapse
That's odd, I've been running for a 2 days without any "spontainious reboots" did you wipe after install or before?

[ROM] [4.4.4] [SaberMod] Mahdi-Rom 2.9 Final...

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my take on Mahdi's great ROM. I love his work so all credit goes to him. I just change a little code to build with SM and maybe add a feature here or there(most have been added into the official Mahdi source. So here you go.​
Features​Built with SaberMod
Everything that is in Mahdi
Change the color of heads up
The OTA Center points to my builds
Smoothscroll
more to come​
Download: My Server
Main Mirror: Basketbuild
GAPPS: My modified PA with ChromeBeta
Other Mirror: Dev-Host - Although original is faster and more up to date
Have a donation? Give it to Mahdi786
cool. thanks!
Great rom, been using for a few days with no issues! Hats off to the op
Gapps inside?
tdamocles said:
Gapps inside?
Click to expand...
Click to collapse
Added link to Gapps
Great ?
Can you insert "Split View" in recent menu?
Greetings
Gesendet von meinem OnePlus One
Stock lock screen please
Some beggin ass mofos around here
amitbhavi said:
Stock lock screen please
Click to expand...
Click to collapse
Stock lockscreen works only on Cyanogenmod-based ROMs e.g. CM11S, nightlies, crDroid, etc.
Mahdi is not based on CM, so your request would be impossible to fulfill :angel:
Just flashed over my existing Mahdi 10/09 ROM.....so far so good!
Prey521 said:
Just flashed over my existing Mahdi 10/09 ROM.....so far so good!
Click to expand...
Click to collapse
Yup same here dirty flash & running great
Did a clean flash, because it looked interesting. I decided to make it my daily driver for a week and see if it can beat Robbie's custom builds.
Already two (very minor) bugs to report:
1. After every boot the double-tap-2-wake gets checked, although I had it unchecked before rebooting.
2. I use the HW buttons and have the backlight at 0% so they don't intrude. Now, also after every reboot, the backlight value gets reset to 100%. Very easy to fix of course, but hey are issues that (I hope) were not supposed to be there.
Hope this is helpful enough!
-Mats
Also dirty flashed, only wiped system.
So far runs great. It's so fast!!
Thanks!
@TiVON, I'm pretty sure the first bug was reported in the official thread.
Thanks for this ROM !
TiVON said:
2. I use the HW buttons and have the backlight at 0% so they don't intrude. Now, also after every reboot, the backlight value gets reset to 100%. Very easy to fix of course, but hey are issues that (I hope) were not supposed to be there.
-Mats
Click to expand...
Click to collapse
I confirme this issue and it comes from Madhi 'original'. The same bug
I have a question, why set DPI so low (280) ? It activates the 'tablet mode' ! 300 DPI is better, don't you think so ?
sd65 said:
Thanks for this ROM !
I confirme this issue and it comes from Madhi 'original'. The same bug
I have a question, why set DPI so low (280) ? It activates the 'tablet mode' ! 300 DPI is better, don't you think so ?
Click to expand...
Click to collapse
Yeah I fixed the dpi for the next build. Sorry about that. I'm not really sure why that happened.
Sent from my Nexus 5
TiVON said:
Did a clean flash, because it looked interesting. I decided to make it my daily driver for a week and see if it can beat Robbie's custom builds.
Already two (very minor) bugs to report:
1. After every boot the double-tap-2-wake gets checked, although I had it unchecked before rebooting.
2. I use the HW buttons and have the backlight at 0% so they don't intrude. Now, also after every reboot, the backlight value gets reset to 100%. Very easy to fix of course, but hey are issues that (I hope) were not supposed to be there.
Hope this is helpful enough!
-Mats
Click to expand...
Click to collapse
I'll see what I can do about that.
Sent from my Nexus 5
Deleted
TiVON said:
Did a clean flash, because it looked interesting. I decided to make it my daily driver for a week and see if it can beat Robbie's custom builds.
Already two (very minor) bugs to report:
1. After every boot the double-tap-2-wake gets checked, although I had it unchecked before rebooting.
2. I use the HW buttons and have the backlight at 0% so they don't intrude. Now, also after every reboot, the backlight value gets reset to 100%. Very easy to fix of course, but hey are issues that (I hope) were not supposed to be there.
Hope this is helpful enough!
-Mats
Click to expand...
Click to collapse
Okay I think I fixed those two problems, we'll see in the next build. I'm trying to figure out why the ota center keeps defaulting to Mahdi's servers even though I have the local and server files I need. I'll build when I figure that out.
xanaxdroid said:
Okay I think I fixed those two problems, we'll see in the next build. I'm trying to figure out why the ota center keeps defaulting to Mahdi's servers even though I have the local and server files I need. I'll build when I figure that out.
Click to expand...
Click to collapse
Great man!
With the same apps, same wakelocks blocked and same kernel, I am getting >20 minutes screen on time more than Robbie's CM11. My new daily driver, thanks!
-Mats
Does this include active display notifications?

YOTA 3 + fingerprint registration problem

Hi friends.
My name is Marcos Feresin from Argentina.
I hope you can help me.
I have a YOTA 3 + global running Android 8.1 with last YetiOS 8.1.0 update from November 13.
Everything worked grate until I did a factory reset and when I must register my fingerprints the process never completes.
It's like it reads the fingerprint but the circle that shows the consecutive touches is stuck in the first read and doesn't advance anymore (the fingerprint icon shows blue movement as reading and vibration but never completes the circle).
I attach screenshots and a screen record of the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gif of the problem:
*ttps://drive.google.com/file/d/1ABfzDdht-aIRDq1ZOn28Cefk7GSAGdiJ/view?usp=drivesdk
Thank you very much for your help.!
MF.-
marcosfere said:
Hi friends.
My name is Marcos Feresin from Argentina.
I hope you can help me.
I have a YOTA 3 + global running Android 8.1 with last YetiOS 8.1.0 update from November 13.
Everything worked grate until I did a factory reset and when I must register my fingerprints the process never completes.
It's like it reads the fingerprint but the circle that shows the consecutive touches is stuck in the first read and doesn't advance anymore (the fingerprint icon shows blue movement as reading and vibration but never completes the circle).
I attach screenshots and a screen record of the problem.
Gif of the problem:
*ttps://drive.google.com/file/d/1ABfzDdht-aIRDq1ZOn28Cefk7GSAGdiJ/view?usp=drivesdk
Thank you very much for your help.!
MF.-
Click to expand...
Click to collapse
Hi!
I had the same problem and I resolved it re-flashing the rom (I have a yota 3 flashed in yota 3+) and registering the fingerprints before the update.
It seems that the problem is in the YetiOS 8.1.0 version.
foraois said:
Hi!
I had the same problem and I resolved it re-flashing the rom (I have a yota 3 flashed in yota 3+) and registering the fingerprints before the update.
It seems that the problem is in the YetiOS 8.1.0 version.
Click to expand...
Click to collapse
Thank you so much foraois!
I'm glad that's a simple update problem but I have a couple of doubts ... first, I never Flashed any ROM on this phone, then I wonder if can I use the same method to convert the yota3 to yota3+ to Flash my yota3+? To fix it like you did.
Or do I just flash a ROM because it already is a YOTA3+?
And what ROM do I must use?
I'm so afraid of ruining my phone because for now there is very little information on this terminal. Maybe I must wait for some OTA update..
marcosfere said:
Thank you so much foraois!
I'm glad that's a simple update problem but I have a couple of doubts ... first, I never Flashed any ROM on this phone, then I wonder if can I use the same method to convert the yota3 to yota3+ to Flash my yota3+? To fix it like you did.
Or do I just flash a ROM because it already is a YOTA3+?
And what ROM do I must use?
I'm so afraid of ruining my phone because for now there is very little information on this terminal. Maybe I must wait for some OTA update..
Click to expand...
Click to collapse
I followed this. It's quite simple.
Unfortunately I'm not an expert, I just read what I found here, so i don't know if you can use the same procedure. (I did it twice, so the second time it should have been as I flashed a yota 3+ from a yota 3+, but...)
Maybe you can try to ask in that discussion, just to be sure.
foraois said:
I followed this. It's quite simple.
Unfortunately I'm not an expert, I just read what I found here, so i don't know if you can use the same procedure. (I did it twice, so the second time it should have been as I flashed a yota 3+ from a yota 3+, but...)
Maybe you can try to ask in that discussion, just to be sure.
Click to expand...
Click to collapse
Ok. Thank you very much for your time!!
marcosfere said:
Ok. Thank you very much for your time!!
Click to expand...
Click to collapse
no prob
foraois said:
no prob
Click to expand...
Click to collapse
I have the same issue after 'master reset'. Is there any solution for this problem?
[email protected] said:
I have the same issue after 'master reset'. Is there any solution for this problem?
Click to expand...
Click to collapse
I saw what they answered you on the other thread. Did you try doing that?
It worked!!!!!
fastboot flash persist.img
fastboot reiniciar
Finger Print Registration ISSUE / Software Update
Hi Friends,
Even I am facing the same problems.
1. The Finger Print is not working, like I cannot add my finger it accept / scan only one time with vibration. { See Attachments }
2. Weather update interval is kept for 30 Minutes or 1 Hour automatically, but it’s not updating. { See Attachments }
3. Double Tap to Lock / Unlock on both the screens, that was one of the major thing which I like in yotaphone2., where i can't find in yota3+.
4. Turning screen (Color to EPD) / button like Yotaphone 3 or unlocking the EPD from front screen in One finger / Swipe like Yotaphone 2.
5. In EPD Screen when we try to drag left (or) right there is a vibration, which doesn’t required need an option to disable.
6. On top of this they have blocked my Wipedata / Factory Reset.
Thanks,
Chenu

Question Redmi 10 128GB

Hello,
i got my mom new phone. After initial configuration + update to latest stock miui, this problem started to show at random. You can hear that touch is working when screen i garbled. I think this is software issue but any suggestions will help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hitmanbg said:
Hello,
i got my mom new phone. After initial configuration + update to latest stock miui, this problem started to show at random. You can hear that touch is working when screen i garbled. I think this is software issue but any suggestions will help.
Click to expand...
Click to collapse
Try restart if it is not working then press power button and volume up button for until Redmi logo appears then reset it through mi recovery
@durga5151 I did factory reset yesterday but the phone still doing this.
Ok, thanks i will try this
If you have warranty ask for replacement.
Is the recovery screen working properly? If not, it's a hardware error.
Hello,
yes fastboot and recovery boot screens work and operate perfectly fine.
Also sometimes it fixes itself after lock/unlock again.
In that case, you need to completely clean your phone and reinstall the system. MiFlash20181115 + the corresponding latest Miui ROM (fastboot = *.tgz). "Clear all" mode.
Yep, gonna do that, i'm waiting my bootloader to unlock and i'm thinking flashing the phone with Pixel Exp. to see if the problem will occur, if not i will reflash with stock rom.
Ty for you help
Did the reflash "Clear all" all was working until i configured face recognition, then problem reoccurred. I think there is
HW problem, maybe with front facing camera.
Bought this phone a week ago and this same thing occurs once in a day and to fix it i just turn the screen off and on and it goes away, judging from this scenario do you guys think if it's a hardware issue? Or it might be a software bug?... Thanks in advance!
Hassanmad said:
Bought this phone a week ago and this same thing occurs once in a day and to fix it i just turn the screen off and on and it goes away, judging from this scenario do you guys think if it's a hardware issue? Or it might be a software bug?... Thanks in advance!
Click to expand...
Click to collapse
first try with reset your phone, if not solved, then flash rom with miflash tool with "clean all" option, if still the problem occuring then, u should go to the service center.
aamnahid said:
first try with reset your phone, if not solved, then flash rom with miflash tool with "clean all" option, if still the problem occuring then, u should go to the service center.
Click to expand...
Click to collapse
I'll try that, thanks!
Two weeks later still no such problem, after i disabled face recognition. Working with fingerprint, no problems.
Ohh, I'm not using the face recognition lock and still getting this once a day, all I'm worried about is if it'll get worse in the future or not.
hitmanbg said:
Two weeks later still no such problem, after i disabled face recognition. Working with fingerprint, no problems.
Click to expand...
Click to collapse
No idea but i did "Clear all" reflash
hitmanbg said:
No idea but i did "Clear all" reflash
Click to expand...
Click to collapse
So if you did clear all reflash and it's not giving this issue anymore that could mean it's probably a software bug
Ps. When it was happening I tried squeezing on the screen with fingers to make it go away as if the screen would properly connect with the connecters but it just stays static and what helps it go away is just putting it in lockscreen and out with the power button.
hitmanbg said:
No idea but i did "Clear all" reflash
Click to expand...
Click to collapse
So it happened again just now making it twice today and i decided i wanna reflash the phone,
Did you flash the stock rom file again or did something else? Just let me know what rom should i flash,

Categories

Resources