Hey!
The Issue: During a phone call the screen turns dark and will not reactivate...it will pop back up after the call disconnects. Hitting any of the site buttons does nothing.
I have tried flashing with the newest firmware (http://blog.geekbuying.com/index.ph...-firmware-released-0502-version/#.UtMOWM93vVI), and although it says this issue has been resolved, it does not fix the problem for me.
I heard that custom ROM fix the solution? (Saw it on this http://forum.xda-developers.com/showthread.php?t=1518663).
But last time I tried one of those, the phone bricked and it took me a while to get it back working (finding stock followed by lost IMEI).
Anyone know a solution? Or possibly a good solid custom ROM that will work? I would really appreciate your help!
I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help
alrightiwill said:
I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help
Click to expand...
Click to collapse
Hey! Not sure if this be of any help, but for me removing the screen (plastic) cover fixed the issue. I assume the screen cover was blocking a sensor thus resulting in my issues.
Just thought I let you know what worked for me...although I doubt your issue can be solved like this.
BTW, I suggest you start a new post, as this one is old and I doubt anyone will read it! also, check out geekbuying.com blog in regards to your phone. They might have more info.
Related
First off, great forum. Been a reader and fan for some time now.
Little question for you all. Looking at the inclosed jpegs, did anyone had this problem with their Polaris camera? I'm wondering if I broke mine, or maybe this is due to flashing a cooked ROM?
Hope you all can shed some light on my problem.
Look at the eClub
Hey Jeat!
Look at the htc eClub, there is a fix for the camera.
I hope that this could fix ur prob.
Frank
Thanks for the tip. Tried it, but that did'nt fix it.
I don't think it had anything to do with the quality of the pictures, but more with a constant overlighting.
No one else had this before?
Take a look at the brightness settings, and the advanced settings -- if you're not clear on how to access these settings, it's in the manual -- maybe you've accidentally changed something in there...
I got exactly the same problem here.
From one day to another suddenly my camera is like that...and i already checked every setting if it might have any influence on the pictures...I couldn't fix it.
Now I'm thinking of sending my orbit 2 back to o2... :/
I had this problem too. All of my pictures were like the one you mentioned. I have tried everything to solve this big problem, without success. After a couple of weeks the camera doesn't work anymore, because of the "Cannot initialize" error. This error is caused by a hardware fault, therefor I have to send the phone back to the factory.
I got exactly the same problem!
Have it with the original ROM and with the udK Diamond ROM, so I really think it's the camera itself.
Too bad we have to send the phone back
Does anybody fix the problem?
if you say its overlighting.. how is it in dark? or how is it in daylight?
Have you tried the finger over the lens and switch off trick to see if it makes any difference?
There are various fixes mentioned but they dont seem to do much. If a hard reset or a radio flash doesnt sort it then its got to be a hardware issue in which case its back to the factory.
Looks like I'm struck with the same problem...
Gonna contact HTC...
(yes I know, this is an old topic.. but problem does still excist)
same problem here..
does anyone know if it is hardware or software issue? i have changed the rom and radio so many times with results. still getting "camera load error", but.. the secondary camera stills works, but with that overlight effect.
im starting to hate my cruise. my old Elfin worked without any problem at all, and i sold it so i could by this crap.
this sucks!
try update your radio to a higher one that may help
I have a completely stock Nexus S. Whenever I answer or place a phone call the screen goes black and never comes back on. I have to remove the battery and reboot the phone. Anyone have any ideas as to the cause of this?
I think it may have something to do with the proximity sensor not being sensitive enough.
Thanks
Sorry for the thread necromancy but it's either that or creating another redundant thread for the same issue. I'm suffering from the same problem as the op (nonrooted Nexus S everything stock) and so are the people who have responded to the informal bug report in the Google mobile help forums you'll get as the first hit if you google "Nexus S back screen after call" (sorry, first post so no links).
I've been unable to remedy it despite quite a bit of research and it's getting quite frustrating, especially since the problem is still present after the update to ICS.
I've gathered this has been an issue with a multitude of handsets and that the problem is on the kernel level and seems to be the result of the proximity sensor being miscalibrated.
Now I don't know how the calibration data is handled on the Nexus S so if anyone is sitting on info related to this I'd love to hear it. Also if there is any way to recalibrate the proximity sensor via ADB or some MMI code that would be great.
Otherwise, has anyone suffered from this problem and managed to solve it by changing kernels? If so which kernel did you use?
Cheers.
Once or twice a day so far, my iris scanner stops working. The red scanner light does not come on when it should, and I get an error pop-up that says "The iris sensor is not responding. Try again later". This happens both from the lock screen and from Samsung Pay when I use iris verification.
Sometimes it recovers after a few minutes. Sometimes it doesn't recover until I reboot the phone, but then it works immediately.
Do I have a defective phone that needs to be exchanged, or is this just a software glitch? Does anyone know of a workaround to reset the sensor when it fails, without having to reboot?
I'm guessing it's probably a software issue. I think there's a system app called "Iris" try force stop on that an see what it does. Has it been happening out of the box or since an update?
Otherwise this could probably get fixed with an update but don't expect them to adress this issue as quick, if you can i would recommend you to just replace the device.
eniorodriig said:
I'm guessing it's probably a software issue. I think there's a system app called "Iris" try force stop on that an see what it does.
Click to expand...
Click to collapse
Thanks, good suggestion. I'll try that next time.
Has it been happening out of the box or since an update?
Click to expand...
Click to collapse
I got the AQD9 update on the first day I had the phone, so there wasn't time for the issue to come up before that.
Otherwise this could probably get fixed with an update but don't expect them to adress this issue as quick, if you can i would recommend you to just replace the device.
Click to expand...
Click to collapse
Yes, unless most other people are encountering the same problem. That's why I wanted to ask here first.
It happened to me once I rebooted and it never happened again. I haven't taken any updates.
My suggestion is , wait until this week's update starts rolling out, if by then you still find an issue I'd recommend you replace the device while you can :good:
eniorodriig said:
My suggestion is , wait until this week's update starts rolling out, if by then you still find an issue I'd recommend you replace the device while you can
Click to expand...
Click to collapse
Which update are you referring to? As I mentioned, I've received AQD9.
Gary02468 said:
Which update are you referring to? As I mentioned, I've received AQD9.
Click to expand...
Click to collapse
Samsung is due to release a major update this week that will fix mostly the red screen issue,wifi issues and mostly first day issues that users are finding. This update will fix major bugs i believe so, so if you're lucky it might just fix the issue you're having but i wouldn't have high hopes. If you get the update this week and the problem persist just get it replaced.
eniorodriig said:
Samsung is due to release a major update this week that will fix mostly the red screen issue,wifi issues and mostly first day issues that users are finding.
Click to expand...
Click to collapse
Great, I'll see how that goes.
More of the same
Like everyone above has stated, I'm sure Samsung will be updating the iris sensor in the near future. I hope they figure out the issue of using it in direct sunlight but as its and IR sensor, it may be impossible.
Force-stopping the Iris system app doesn't fix it when it stops working. Neither does clearing that app's cache. I'll try clearing its data and re-registering my irises, but I'm not optimistic.
As of this morning, I get a slightly different error message, "Can't use iris recognition", when the red light doesn't turn on. It seems to happen most often following a prolonged idle period (e.g. overnight). Rebooting always fixes it immediately.
I notice other threads describing a similar problem with the fingerprint sensor. I've only encountered it with the iris scanner. But if it occurs with both, and both are fixed by rebooting, that makes it more likely to be a software issue.
RootTheS8+ said:
Like everyone above has stated, I'm sure Samsung will be updating the iris sensor in the near future. I hope they figure out the issue of using it in direct sunlight but as its and IR sensor, it may be impossible.
Click to expand...
Click to collapse
Won't happen unfortunately. The sun emits a lot of infrared and I assume it would look very similar to how your own camera sees the sunlight, with massive glares forming on the lense making it hard to see any other details with a lense flare taking up most of the image. I have a filter to allow more infrared but less visible light to pass through the lense, maybe I'll tape it on and see if it works better, but it's doubtful.
Bump. Any insight on this issue? I just experienced "Can't use iris recognition" for the first time on my week-old S8+ (latest stock firmware).
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Have you tried resetting the phone ( as in completely wiping out everything including OS) and then try installing MIUI, if it still persists try a custom ROM
Same issue here, China version in use and went to 10.3.9.0 where issue popped up. Tried to go back 10.3.5.0 but issue still exsist. Absolute annoying issue and makes phone totally unusable.:crying:
resetted of phone and etc, but no help.
Mine's now in a drawer, awaiting any form of fix.
I bought an Umidigi F1 Play while waiting......
Terrible issue and absolutely no support from Xiaomi.
Have personally owned Xiaomi phones since the Redmi 2 and never had any issues with flashing software.
Never again.
Try to flash china rom lowest version of miui 10 which is stable. Works for me.
Does not help, lowest u can flash is 1035 which will not fix the issue.
EDIT: flashed custom ROM, still issue persist
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Looks like there's a hardware defect in your device, maybe you got a faulty device, try going to a recognised mi store and get it replaced
This is not hw defect, mine was fully functional before firmware update to 1.0.3.9.
mlackke said:
This is not hw defect, mine was fully functional before firmware update to 1.0.3.9.
Click to expand...
Click to collapse
What If the phone was dropped or smth..
Hi,
I have the same problem which occurred after update.
Bump. Has there ever been a software-related fix to this issue? I currently have the same problem as described by the OP on a XIAOMI MI 8 Lite (128GB, 6GB RAM), although it only appeared after unlocking the bootloader and flashing a custom recovery. I've been flashing ROMs for quite a few years now and also double-checked all the software I've been using, I am certain that I made no software-related mistake. Since encountering the issue I have reflashed various original stock firmwares from xiaomi using both the flashtool and twrp, all to no avail. I've even relocked the bootloader, just to be absolutely certain. Since the entire touchscreen still registers input, I find it hard to believe that it is a hardware related issue, especially since I never dropped my phone and it also never experienced any physical trauma (so to speak). Would really appreciate any further input.
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
mlackke said:
Same issue here, China version in use and went to 10.3.9.0 where issue popped up. Tried to go back 10.3.5.0 but issue still exsist. Absolute annoying issue and makes phone totally unusable.:crying:
resetted of phone and etc, but no help.
Click to expand...
Click to collapse
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
Has anyome fixed that yet? Is it even possible? I have tried everything, dowloaded tons of GB of roms, flashing programs, watched milion vids on YT, and still cant find anything. So i you find somethink, let me know <3
Prakashr09 said:
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
Click to expand...
Click to collapse
Is there any update ? Strange thing is, it seems not that many devices have this problem ... or I couldn't find other threads about this
Anyone here getting ghost touch issue and sometimes proximity sensor issue too?
I tried with different firmware as well as stock miui and custom...
Upto 12.0.7 I didn't face that issue ..
After 12.0.8... I think my phone evolved into android robot
Oh man, it is automatically working
rhudsonsamuel said:
Anyone here getting ghost touch issue and sometimes proximity sensor issue too?
I tried with different firmware as well as stock miui and custom...
Upto 12.0.7 I didn't face that issue ..
After 12.0.8... I think my phone evolved into android robot
Oh man, it is automatically working
Click to expand...
Click to collapse
I didn't have that problem.
btw you posted in the wrong place.
Huh?
Posted in X3 thread only!
I have faced that issue too, but my phone has been dropped already and has a broken screen in the bottom. I guess this could be the reason my scenario.
Not a single damage on display.
now trying with latest firmware with custom rom and up to this time I didn't face it..
proximity working well
I have also ghost issue for months. It start after 5 or 6 months. I saw a lot of threads on reddit, and some here for other POCO or X3 Pro.
My issue is that sometime, 1 or 2 times a day, the screen goes crazy. Touch appears on all the screen and the only solution is to lock and unlock the screen.
I tried to disable 3 touchs option, stays à 90Hhz, update rom... I even tried to RMA but my local official xiaomi affiliated can't reproduce the issue.
At last I tried to install ArrowOs but crazy ghost touch reappears after 2 days. Do you think we can find some kernel or "touch driver" that can help ? What for an "indonesian" rom ?
It's a Hardware Problem.
I'm still looking for a way to mitigate this issue.
I just have to shut down the screen and then it's ok. It could be a software solution to reset some memory or electric level somewhere.
I saw tens of reporting, it look like a common issue on POCO device
Try and install: Touch Improvement magisk module of Akira
I think it need time for it to work right (somehow), but I don't have any issues anymore, while my phone was flipping like...
You're welcome! ;-)