Hey I have an amazfit pace and the backlight brightness stop working ... I tried to change ROMS but it's without a difference. Any ideas?
I don't understand why so many people think that re-flashing firmware would fix such issues... It is simple: if you factory reset without restoring old data and it still doesn't work then it is dead, it is a hardware issue, nothing that you do with software or firmware will make it work.
Related
First post.
My wifes Samsung Galaxy S2 LTE from Rogers (i727R) which came with 2.3.5 got some water spilled on it. After letting it dry out the phone works fine but the camera just gives a "camera failed" error and the screen auto rotate doenst work at all in any app.
I got the camera working for a bit after doing a factory reset but but it stopped again a few days later. This made me think it was a software issue so I rooted the phone and tried flashing the stock rom back on using Odin which did not help either issue. To rule out that it is corrupted software, is there anything else I should try? New kernel?
When I enter *#0*# and go into the sensor test area, the accelerometer and magnetic sensors do not seem to be working. Gyroscope is working.
If more info is needed, let me know.
Thanks
Use this app to test if they are working: https://market.android.com/details?id=com.bartat.android.elixir&hl=en.
Thanks for the help. I installed elixer and looks like the accelerometer, gravity, linear acceleration, magnetic field, orientation and rotation vector sensors are not working.
Dyno-droid said:
Thanks for the help. I installed elixer and looks like the accelerometer, gravity, linear acceleration, magnetic field, orientation and rotation vector sensors are not working.
Click to expand...
Click to collapse
So that means it's a hardware problem. You'll have to carry it back under warranty (hopefully you have one).
That brings me to my next question.
I rooted and flashed the stock rom on with Odin, hoping that would fix it since the issue was initially fixed with a factory reset. Thought maybe a driver or something got corrupted.
From browsing the forums, it appears there is no way to reset the flash counter yet. Is that correct? If so, would it be worth waiting a while in hopes a fix comes out to reset the counter?
Dyno-droid said:
That brings me to my next question.
I rooted and flashed the stock rom on with Odin, hoping that would fix it since the issue was initially fixed with a factory reset. Thought maybe a driver or something got corrupted.
From browsing the forums, it appears there is no way to reset the flash counter yet. Is that correct? If so, would it be worth waiting a while in hopes a fix comes out to reset the counter?
Click to expand...
Click to collapse
Only a few devices are able to reset the flash counter (so far). You could try flashing a custom rom and see what happens.
NB.: Even if you could reset the counter, that wouldn't really benefit you in this case.
Hey guys,
I know this thread already exists in this forum but has come to an end with no solution and since its kinda very important to sort this issue to be able to use my phone I thought ill start fresh for some input from the experts.
I have a Galaxy S2 I9100 rooted with a custom ROM(slim ICS 4.1 when the issue started) and it started randomly freezing when unlocking the screen and normal use .but since last week it wouldnt let me make or receive calls as the phone freezes and reboots 10-20 secs into the call..i updated to 4.2 with the hope of resolving this but tht didnt work..I have changed kernels and ROMS(resurrection, cm9 release build)..though the dialer did work for calls on resurrection ROM the proxomity sensor wouldnt work..
so i tried going back to stock sammy ICS (XXLPH) and then the dialer would work but again without the proximity sensor and the samsung tests also confirmed that the sensor wasnt registering...
am rooted now and back to slim 4.2(dont like the look of sammy) with siyah kernel 3.2.2...the dialer and proximity sensor don work..the rest of it is all fine..
Ive done all the wipes each time ive installed a new ROM...also done kernel wipes before installing Kernels..
I think its not a ROM/hardware problem but well it could be but hope to get it sorted through the normal techniques..I cant return my phone for repairs as it was in mint condition bot second hand in UK without warranty papers..
Any help would be highly appreciated..thanks
EDIT: It seems the proximity sensor is to blame for this problem as i found out through other posts..and also i can make and receive calls with the headset/headphones plugged (in which case i assume the phone doesnt try to activate the proximity sensor)..
For now i would like to know how to disable the proximity sensor on the phone..I have tried inserting the gsm.proximity.enable=false in the build.prop editor using the ROM Toolbox lite app n rebooted...but that din seem to work...is there any other way to do this??pls help
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
proximity sensor and screen brightness sensor
3dawg said:
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
Click to expand...
Click to collapse
I havent managed to find a solution as yet..it seems the proximity sensor and the screen brightness sensor(which are on the same PCB i think as per the unassembling video) have a hardware fault and might need repairing..
Some kernels i think maybe bypass using the proximity sensor if its not working..for now I am back to the SLIM 3.2 ICS rom..It doesnt switch off my screen on call and also no auto brightness adjustment but rest all works ok so am using it for now before i get the hardware repaired..
also the resurrection rom v 2.5.1 works fine in the same manner(havent tested many others..CM7 release build doesnt work)..or you can try that script in build.prop to disable the proximity sensor..
check how it goes..
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
proximity sensor and screen brightness sensor
3dawg said:
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
Click to expand...
Click to collapse
I tried checking with the testers for the Slim ROMS..regarding differences in kernel or anything for slim 3.2 and 4.2(3.2 works while 4.2 doesnt) but they couldn't tell me what was the exact problem or the differences that should affect in this case..I haven't tried a CM9 ROM yet but it could work..The kernel for the resurrection ROM is siyah kernel but when i tried that kernel with the slim 4.2 ROM that still didn't work for calls as the phone rebooted.
Have you managed to find a replacement cost for the proximity sensor? also does your screen brightness sensor work?
Hi everyone. Compass is stuck in my s4 mini. From sensor test (*#0*# then sensors) I can see this (see attachment). It seems like magnetometer is not calibrated. Any way to calibrate it (apart from usual methods like 8 figure or rotate phone around tre axis since I already tried them and they didnt worked) or reset it to stock values? Tried factory reset too.
thanks a lot guys.. I really need help, It may be an hardware issue but I want to try everything via software before send it to sammy
Attachments are in this other thread: http://forum.xda-developers.com/galaxy-s4-mini/help/gt-i9195-compass-properly-possibly-t2861288
Please help
I have screen rotation problem,samsung s2 gt-i9100, android version 4.1.2. Screen rotation works sometimes on strange angles. Already tried calibrating but still not fix.
I tried flashing another kernel to solved the problem using SiyahKernel S2-v6.0beta5 but it doesnt rotate anymore no matter how i tilt the phone. I've been repeatedly doing restore factory settings, wipe cache stil not solved.
I've tried dialing *#0*# and go to accelerometer sensor, it seems okay, the needles are moving. I've also tried installing "bubble level" app, the bubble moves, the sensor seems okay.
Again, tried flashing another firmmware XXMS7 Android 4.1.2 Jelly Bean but still not work.
Is there another solution to this problem?
Hi
anyone else encountering camera failed while using the camera. im kindda dispointed and didnt expect a phone high standard as the s9+ will still have this problem. been using my p20 pro camera for many times and never encounter this kind of error. any suggestion how to avid facing this problem
olygopoly said:
Hi
anyone else encountering camera failed while using the camera. im kindda dispointed and didnt expect a phone high standard as the s9+ will still have this problem. been using my p20 pro camera for many times and never encounter this kind of error. any suggestion how to avid facing this problem
Click to expand...
Click to collapse
Did this just happen out of the blue or has it always happened? Did this just happen after an OTA update?
Did you modify the phone at all (root/etc)... did you power cycle the phone, clear cache partition, try doing the factory data reset the phone?
If software issues can be ruled out then it's very likely a hardware issue. You will have to have the phone serviced.
scottusa2008 said:
Did this just happen out of the blue or has it always happened? Did this just happen after an OTA update?
Did you modify the phone at all (root/etc)... did you power cycle the phone, clear cache partition, try doing the factory data reset the phone?
If software issues can be ruled out then it's very likely a hardware issue. You will have to have the phone serviced.
Click to expand...
Click to collapse
Happen out of the blue. Did happened before the June update and apparently after the June update. Not root. already clear cache but didnt do factory reset.
olygopoly said:
Happen out of the blue. Did happened before the June update and apparently after the June update. Not root. already clear cache but didnt do factory reset.
Click to expand...
Click to collapse
If you do the factory data reset be sure to try the camera at the default settings... Try it a few times to make sure that it works (or doesn't work) more then once. If it works with default settings then make a change to bring it closer to what you had it at before.
Ultimately your trying to see if it is a software issue (a setting) that is causing you the problem. By making small changes here and there you can know which change caused the issue. Making more then one change at a time will make it harder to narrow down the cause.
The Factory Data Reset will hopefully resolve any software related issues on the phone. Try to not use a smart switch backup, it may cause the problem to come back again. I ran into this with my dialer app hanging up on all outgoing calls... FDR without using a smart switch backup worked perfectly, using the smart switch backup just caused the problem with the dialer to happen again.