Related
first, sorry for my english
Camera Flash does not work with any ROM...
I tried all the ROMS available ... stopped working after the Chinese ROM Froyo 2.2, But now no longer works with any ROM, or 3.4.2 UK or Roms Eclair etc...
But I can not access the Developer Forum, I've put it here ... I know there are more users having the same problem
Repeat, sorry for my english and Thanks for the Help.
I have exactly the same problem. Since china 2.2 sbf and rom, every rom and firmware exhibits the flash either not working on apps, or is out of sync with a blue tinge. I've tried every combination of fixes out so far, but nothing works. Will keep trying things out and post here if I find anything.
Sent from my MB525 using XDA App
Foxhound.kl said:
I have exactly the same problem. Since china 2.2 sbf and rom, every rom and firmware exhibits the flash either not working on apps, or is out of sync with a blue tinge. I've tried every combination of fixes out so far, but nothing works. Will keep trying things out and post here if I find anything.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yes, I saw in the other section you had the same problem .. several days trying things and more things, and ROMS of all types, but does not work any ways ... will have been spoiled by Hardware? coincidence as the Chinese Rom
On me, the flash does not work none time, only a very small light blue-green
If you find anything, any minor detail, let me know please.
Thanks
I have to test more, but mine has low light and light borders are greeny.
Sent from my Defy using Tapatalk
Have the same problem. Flashed the chinese rom just a few days ago following a guide and the flash is now weak and greenish even when I'm back on my stockrom.
Whats strange is that I tried this rom following a guide several weeks ago, flashing only the 2.2 bootloader and using a nandroid backup. The flash just worked one time, so I went back to my stock rom, 2.21, again and the flash worked as before.
I think I have tried flashing the whole chinese rom and then gone back to stock with no prob before also. It was just this last time the flash stopped working as it should, no matter witch safe rom I now flash again.
I have tried the uk 2.2 with dowgradebility to get the flash working as explained by Higgsy but no go.
The only thing I can think of is that when you try to use the flash to many times when you are on the chinese froyo rom the flash gets damaged somehow.
Sent from my Defy
Did you guys notice that there's a black or dark yellow spot in the middle of the flash light? Many people who had this weak green light problem reported that their flash lights are like so because it's been burnt.
mimel said:
Did you guys notice that there's a black or dark yellow spot in the middle of the flash light? Many people who had this weak green light problem reported that their flash lights are like so because it's been burnt.
Click to expand...
Click to collapse
Looking at the LED, there's a slighty darker yellow spot in the middle, but not that dark, just a slight shade above the outer part. Not sure if its burnt out to be honest, becasue when the flash does work, its pretty bright and lights up what i'm pointing it at, but the moment the camera captures the image, the flash is already off, so its just not in sync with the image capture. The blue/green tinge comes after the bright flash, just as it ends. Can you tell me where the burnt out LEDs are being reported mimel?
I have it all yellow, I no see black spot.
Since the Chinese Rom, did not run the Flash, no weak, no strong, not be in sync, none of this, only not work, only shows a very very small light blue-green.
I would like to see a picture of a burned Flash.
Thanks for all the help and sorry for my English.
Yours probably is not burnt and might get back to normal by flashing the latest T-Mobile or uk sbf.
A burnt flash light can flash everytime but with very weak white light and ends with green/blue. It's unrecoverable even upgraded to the latest sbf or downgraded to 2.1.
Foxhound.kl said:
Looking at the LED, there's a slighty darker yellow spot in the middle, but not that dark, just a slight shade above the outer part. Not sure if its burnt out to be honest, becasue when the flash does work, its pretty bright and lights up what i'm pointing it at, but the moment the camera captures the image, the flash is already off, so its just not in sync with the image capture. The blue/green tinge comes after the bright flash, just as it ends. Can you tell me where the burnt out LEDs are being reported mimel?
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
mimel said:
Yours probably is not burnt and might get back to normal by flashing the latest T-Mobile or uk sbf.
A burnt flash light can flash everytime but with very weak white light and ends with green/blue. It's unrecoverable even upgraded to the latest sbf or downgraded to 2.1.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
It is not my case, I have tried all the ROMS and does not work .. do not see any white light, only a very very small light blue-green.
I tried all the ROMS, I have the UK currently 3.4.2, but I also tried the T-Mobile and earlier ones, spent several days doing tests ...
I had the similiar trouble, only first flash and then a reboot was needed. Finally I managed to have normal flash.
What I did?
It is not just sufficient to flash another rom, but to meticulously follow a recipe. In this case I went from 2.21 Stock Rom Central Europe to 2.34 JIT Version, flash still normal. Then Chinese 2.2 ROM, flash only at first time, then reboot needed. I went back to 2.34 JIT Version, flash normal again. Then after a while when the UK 2.2 version came out, I still waited till Higgsy found out how to circumvent the flash troubles: http://forum.xda-developers.com/showthread.php?t=934366
It is for all people who never flashed a non downgradable 2.51 UK Version.
Just follow meticulously every step in Higgsy thread. If flash is working, please inform us here we also need positive affirmation
vince89 said:
I had the similiar trouble, only first flash and then a reboot was needed. Finally I managed to have normal flash.
What I did?
It is not just sufficient to flash another rom, but to meticulously follow a recipe. In this case I went from 2.21 Stock Rom Central Europe to 2.34 JIT Version, flash still normal. Then Chinese 2.2 ROM, flash only at first time, then reboot needed. I went back to 2.34 JIT Version, flash normal again. Then after a while when the UK 2.2 version came out, I still waited till Higgsy found out how to circumvent the flash troubles: http://forum.xda-developers.com/showthread.php?t=937319 In the meantime, this thread is altered again, from a full stock 2.2 UK version do a deblured variant but I believe it still works as a remedy for flash troubles.
It is for all people who never flashed a non downgradable 2.51 UK Version.
Just follow meticulously every step in Higgsy thread. If flash is working, please inform us here we also need positive affirmation
Click to expand...
Click to collapse
This process of Higgsys has been followed many times by myself, and I still have this flash issue. Problem is that when 2.1 firmwares are flashed via RSD Lite, the flash issue remains, and not working as usual as you and Higgsy have described. I'm going to try to uninstall the windows drivers and RSD Lite, reinstall these fresh, and then start the whole process again to see if that makes any difference.
Sent from my MB525 using XDA App
In my case, I have the ROM 3.4.2 UK and this ROM is not "downgrade" but I followed the steps of Higgsy and I do not work, I think my case is different from yours and my Flash is Burnt ...
Thanks for you help...
I think it must be burnt as I have never used the camera flash fixes in some of the ROMS when the camera flash was dodgy and now I am higgsys 3.4.2 ROM and all is good. Cheers
Ok, so I'm still facing this problem on my phone where the camera flash is either out of sync, which flashes brightly too early before image capture, and takes the picture as if no flash was on at all. This occurs on all camera apps on all ROMS installed will all methods, and the flash doesn't work at all on any flashlight apps.
After doing some research, I have found similar issues on other motorola phones, which may or may not help in this regard.
There seems to be a cutoff to the flash reported on Droid phones, either disabling or weakening the flash if the battery threshold is below 30-40%. When the phone has a higher charge than 30-40% or is plugged in to charge, this has eliminated this problem. It seems the driver to the camera flash can determine what your battery level is, despite what your phone is reading out, so if your reading is inaccurate, the flash will cutoff or weaken if below this threshold.
To solve the battery indiactor inaccuracy, follow the steps in the link below using ADB or Clockwork recovery to reset battery stats. Instead of turning off the phone when instructed, take the battery out of the phone for 10 secs and put back in for good measure;
http://androinica.com/2010/02/11/tip-how-to-fix-your-androids-battery-issues-rooted-devices/
Don't know if this will work for people with the flash problem on the Defy, but its worth a try. I haven't tested this. I will later and report back.
I was thinking about the build prop as well, as this seems to feature some lines pertaining to the flash intensity, as quoted by mflich in another post;
mflich said:
hi
i have a defy with 2.21_UK.And when i saw this patch i decide tu up to 2.2_Chinese.
but when i finished it the flash just worked at the first time of reboot
so i want to patch it but i can't enter the custom recovery(at that time i didn't know it's because of USB debugging)
and then i flashed 2.51_UK. but the flash didn't work too.
at this time i can only recovery 2.2 or flash 2.51 and the flash works with low intensity in green light
i noticed that the flash fix is some file in system and i can't read the file with .so
but i found that in build.prop there was some line like this:
ro.media.capture.maxres=5m
ro.media.capture.flash=led
ro.media.capture.classification=classH
ro.media.capture.flip=horizontalandvertical
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
but in the same file in 2.21 there are the only two lines:
ro.media.capture.maxres=5m
ro.media.capture.flash=led
so i guess it's because of the differents in this file my flash doesn't work
and the num 41 25 means 41% and 25%?
and what does the classification and flip mean?
with this can i make my flash work again?
sorry for my poor english
Click to expand...
Click to collapse
Can anyone else with flash problems see what is stated in their bulld prop lines for the flash? Maybe we can alter some values to solve our problems?
My flash dont work on today, But I dont have problems synchronizing or low light intensity, light Does Not Work, That appears on the flash is so so small That Is Not Appreciated in a dark room completely.
I think there has been "melted" FlashLED, this strange yet it seems that happened to me when I put the Chinese ROM Froyo and since then no work with any other ROM.
If I indicate that I can do tests to try to fix it, I will.
EDIT: Where are these lines? as I can watch them?
Sorry for my english!!! ... and thanks for the help!
Darkcaptain said:
EDIT: Where are these lines? as I can watch them?
Click to expand...
Click to collapse
You need the PropEditor-0.3.apk from the follwoing link. Be really careful with this, you can modify your system files and possibly brick your phone. Make a backup of your .prop first in this app before making any changes.
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
I have the same issue with the flash that you, Foxhound.kl. I found a temporal solution to the desync. I turn on the led with the tesla app, and then i launch the camera with the auto-flash enabled.
After the first photo the led is turned off, but the tesla app keep running in the background and some way make the flash to be sync and work properly in the other photoes.
Sry for my english.
Appears to me the same thing:
ro.media.capture.classification=classH
ro.media.capture.flash=led
ro.media.capture.flashIntensity=41
ro.media.capture.flip=horizontalandvertical
ro.media.capture.maxres=5m
ro.media.capture.panorama=0
ro.media.capture.shuttertone=1
ro.media.capture.torchIntensity=25
Click to expand...
Click to collapse
ro.media.capture.classification=classH
ro.media.capture.flash=led
ro.media.capture.flashIntensity=41
ro.media.capture.flip=horizontalandvertical
ro.media.capture.maxres=5m
ro.media.capture.panorama=0
ro.media.capture.shuttertone=1
ro.media.capture.torchIntensity=25
I also have these same values.
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.
all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?
Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue
Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )
A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing
webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!
HTC desire 816 touch screen not working properly, have to press several times each button. i bought this mobile this november 2014, instead of samsung S4, i bought this HTC, but it is irritating me lot, i tried for phone reset also, but getting same problem, im planning to go to show room for replacement,,,,,.......
Sir,
Please wait until mods will move this thread to the device specific forum.
For reply or more questions please register an account on XDA forums.
Stand by
Good luck
I have this problem to please help me to fix this
Sent from my iPad using Tapatalk
Haji Mohandes said:
I have this problem to please help me to fix this
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Same problem here. Typing a message is very hectic. Any body please help us if you have a solution.
Faisal
faisal892 said:
Same problem here. Typing a message is very hectic. Any body please help us if you have a solution.
Faisal
Click to expand...
Click to collapse
I just resolved this issue with help of mygamers. As advised by him I download stock 1,58 kernel from here https://www.androidfilehost.com/?w=...20a0dd4400e309e7d0fd260a360ef37e06faf2f86678f. I flashed it and now my cell phone's touch screen is working perfectly. My cell phone is HTC Desire 816 a5_dug. Try it, it may work for you as well.
Faisal
faisal892 said:
I just resolved this issue with help of mygamers. As advised by him I download stock 1,58 kernel from here . I flashed it and now my cell phone's touch screen is working perfectly. My cell phone is HTC Desire 816 a5_dug. Try it, it may work for you as well.
Faisal
Click to expand...
Click to collapse
Thanks for reply
I do that but my problem not solved and get very bad
Sent from my iPad using Tapatalk
Plzzzzzzzzzz heeeeeeelppp.. I'm with the same trouble I think is not a hardware issue..
Same issue here, 816x Asia. After any Rom I flash I get this a few mins after boot. Only on stock it works perfectly. I tried different kernels with roms and used 2 kinds of recoveries. Most recent versions of twrp and cwm ... Any ideas?
same problem on build 401.
I have same problem.I guess that was happen after 150MB update.
same problem
same problem plz help !!
does anybody found solution?
after flash stock kernel 1.58,left side of touch screen disabled.
God damn HTC.I bought this phone as gift for my wife.
maybe you didn't flash quite the right ROM. try updating via OTA
touch bug
seekfind said:
maybe you didn't flash quite the right ROM. try updating via OTA
Click to expand...
Click to collapse
have same problem on all different roms (carbon, cyanomode, pacs, miui, etc....)
exactly.what is the problem?software?or hardware?
does anybody test different kernel? I used stock kernel that was downloaded it from Internet.left side of screen disabled.
This does seem to be a Kernel problem; more specifically, the kernel not being compatible with the Rom or your specific hardware variant.. the only thing I can think of is an RUU exactly for your variant will solve all the problems. your phone's warranty is void so you can take it to HTC care (like Yas mobile in IR) so they flash the right RUU for you if you can't find it here. after getting the RUU, you can safely update to 1.58 via OTA to fix any remaining problems becasue it're really stable and bug free
I have the same issue. No one seems to know what it is. i am on the 816x asia single sim. I have tried stock kernal, garak kernal. CM11 CM12 Miui, Carbom. same thing happens. After i get through set up (time frame 5 mins tops) the touch screen stops reacting correctly. IE having to touch things more than once, swiping becomes harder and if i go into the pointer location DEV tool i can see that holding my finger in one spot it sparatically bouces around. Only on the stock rom the touch screen works fine. i have recovery 6.0.5.1 CWM i have tried flashing on TWRP. I am guessing this could be a 816x firmware issue. maybe this touchscreen isnt the same driver as the other htc's or if the source is packing the galaxy ts driver this is reacting to this version of phone. A guess at best.
thanks my friend.I think that it is a software problem,too.(I hope!?)because htc hardware quality is good.
does anybody tell this issue to HTC?
Buzzzz
masoudamirian said:
thanks my friend.I think that it is a software problem,too.(I hope!��)because htc hardware quality is good.
does anybody tell this issue to HTC?
Click to expand...
Click to collapse
From what I understand, This issue has nothing to do with hTC anymore. They have fixed the touch problem on their latest update (1.58). but if you install custom roms or backups not specifically made for your device, it is possible that you will have incompatible versions of HBoot, Kernel and Rom. this will lead to the situation that even after updating to 1.58 you'll still have the touch problem. now you can do several things to fix it; one is to try and find the suitable backup and after restoing that backup, update via OTA to fix the problem. another one is to install the RUU and then update via OTA. if you can't find the files or find the process diffiicult, you can take it to HTC care and explain that you need the RUU flashed and let them do it.
I've heard that they can even do it over the internet but I haven't tried personally
cm12 system UI crashes desire 816
I'm on cm12 nightly on my desire 816 dual sim wenevr I click on mobile network option in my settings the system UI crashes and I loose my network..... This happens each time I try it...n den I have to restart my device to get back my network....is der any solution to fix this prob so I can access that option in setting without crashing system UI
Thank you in advance
I am using Pixy Os 9.0 on Default Kernel And Phone Sensors are stopped Working like (accelerometer, proximity etc.).
I've tried going back to Oreo roms but not success.
Should I try changing kernel or something?
Try flashing this
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
That worked. Thank You
That sensor flashing is easy way. However I took a different time consuming way. Writing it down so that it may help some one else.
When I switched from Oreo AiCP to latest Pie AEX, I went via the hard way. You may read it here https://forum.xda-developers.com/le...bootloader-t3868174/post78256476#post78256476
AEX 6.0 worked well but I too was facing sensor issue. I re-flashed the ROM but no effect. CPU-Z sensor page was complete blank. Yes, I knew the sensor.zip available for flashing but I went ahead to REDO the entire ZUI 1.9 to AEX flashing process.
This time around, all sensors are working fine.
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
mirkios said:
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
Click to expand...
Click to collapse
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
satyen_ said:
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
Click to expand...
Click to collapse
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
mirkios said:
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
Click to expand...
Click to collapse
I think the issue is not with any ROM, it is due to the screen and all other replacements, may be after the replacement your proximity sensor is always covered or blocked with something. There are apps on playstore to see the proximity sensor data check if the always shows the same distance/reading i.e. 0 while waving your hand over it, and if yes then the issue might be what I mentioned above. If that's the case you would have to take of the screen and adjust the proximity sensory properly.
Check with this app :
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
I have AOSP 10 on my ZUK. The sensors did not work.
Thank you. Now everything works well.