Before rooting, I tried to use the Samsung built-in test (From dialer, dial *#0*#).
Most tests passed but I had issue with the following:
1) Sensor > Gyroscope sensor > (Gyro SelftTest)
2) Magnetic Sensor > Power Noise Test
My Gyroscope was calibrated already - (See attached images.)
Note:
I ran those tests many times and they failed on all of them. One time I ran them they passed but it was the only one.
Can anyone else confirm those tests? Also it would be nice if anyone knows a bit more about this to explain if it's a hardware problem or not.
Thanks.
In the meantime, are there any well-known hardware issues I should check prior to rooting?. I checked most basic things like phone, sms, etc. but I don't know if there are any frequent issues like my HTC One X had.
IT doesnt matter with the S3 if you find an issue its easy to unroot and hide the fact you have installed a custom rom.
Related
Can anyone show me how to enable in-call softkey function??? During call, my display is off and cannot use softkey, if there is an extension number, I have to wait until operator pick up or even cannot see which number is calling via call waiting function.
My ROM is original HTC ROM, don't ask me to load cooked ROM
Thank you
Did it ever work before?
This is the standard:
The display turns off once you put your device close to your ear.
Moving away again should turn back on the screen.
Now there are 2 possible issues:
1) The sensor is malfunctioning
2) The driver/system is malfunctioning
Since you don´t mention if the problem arose after you did something, one cannot offer you better help. Maybe you already tried a hard or a soft reset?
Thanks tictac,
I did upgrade firmware and problem temporary solved
Hey Mongoose,
First of all, great job with the ROM. Installed both Alpha 2 and 3 and you are making fantastic progress!
Thanks also to all of the Eris DEVs (and all DEVs for that matter) out there, my first little Android has held its own for a few years now
A quick comment:
The keyboard consistently opens ALMOST all the way up. For me, it's been stopping in the middle of the last row - still able to use - but not fully visible.
I was in the Messaging app and I did something that made it jump up to fully visible, but now (of course) I can't replicate what I did.
Thanks again, looking forward to future iterations!!
Wanted to comment on what I've tested and is WORKING for me:
touchscreen (not having any of the reported issues)
physical & soft buttons
data
calls (sending and receiving, no mic)
earpiece audio
sms (sending and receiving)
vibration / haptic feedback
proximity sensor
google sync
root access
NOT WORKING:
microphone
speaker audio
wifi (scans fine, can enter text to connect, says it's connecting, then authenticates, then loops on connecting/authenticating)
gps
camera
bluetooth
trackball
light sensor
orientation sensor
accelerometer (downloaded an app that has opengl 3D using the accelerometer and it rebooted the phone when I tried to view the 3D model)
magnetic field sensor
sdcard
mms (when I choose attach a picture it says "No external storage available.")
Also, installation was a piece of cake!
Wiped data and dalvik and then let it boot. Obviously no boot animation, but first the screen illuminated, then the soft buttons lit, then the haptic feedback shook, and then I was at the Start screen.
Again, fantastic job!!
Hello all,
Just to clarify (since some people in the Dev forums are still having issues that I have not had with Alpha 3) my Eris model number is PB00100.
I believe this is the 2nd model number of Eris from Verizon (not 100% sure about this)? I did have my original Eris replaced after I was losing calls like crazy.
Hope this helps!
Thanks for the detailed feedback! With another post you'll be allowed to post in the section. Look forward to seeing you over there
No problem! Last night I was following the dev thread in the Hero forum talking about the audio issues. Looks like jaybob413, Shelnutt2, shed, you, and a couple others are very close to working that issue out.
Once this build has a working mic, I will be using it more extensively.
I did search, so apologies if this has already been asked.
Since updating to ICS, neither auto-rotate nor automatic brightness are working.
I have checked the relevant settings, and both were definitely working under Honeycomb.
I've also tried Elixir - which reports all sensors as unavailable except the microphone - and a few calibration utilities, none of which seem to have been effective.
So if anyone else has had this issue or has any suggestions, or can confirm any calibration tools that work for you, please let me know!
welcome to our sad and dark world
http://www.transformerforums.com/forum/transformer-prime-help/13507-autorotate-problem-4.html
I'm having issues with my screen rotation and everything associated with the gyrometer/acceleometer, I'm struggling to find the part in my phone, I've downloaded the repair manual but its not listed. Can anyone help?
Thanks
Ps I've tried everything software based with updates and resets, so must be hardware issue
I bought Xperia x a few weeks ago and I found audio output through loudspeaker is less compared to other phones out there. So I contacted sony care online and they told me to do speaker diagnosis test available in settings app. While testing I wasn't able to hear anything from speaker. Does that mean that my loud speaker has problem? Can anyone out there check and confirm that diagnosis test works well or not for you?
I tested this from diagnostic app in settings and I could hear both speakers.
Yes, both speaker should work (assuming your volume level >0). I am afraid you must return your phone.
I would respectably disregard the previous suggestion to return your phone as this appears to be an issue with Sony's app and nothing at all to do with the stability of the hardware itself.
When I first ran the diagnostics, all tests except the proximity sensor passed; including both speaker tests. I restarted the phone, reran the test, and the proximity sensor test passed without further troubleshooting. Unfortunately this time both speaker tests decided to randomly fail? I called my voicemail and the earphone speaker worked without issue, so I then turned on the loud speaker and it also appeared to work just fine.
I did this a couple more times and got the same results so I decided to troubleshoot the issue a bit further, and what I found was that Sony's app appears to wrap around built in diagnostics commands; which are the same commands that can be accessed and/or ran via the "Service Menu". After running both speaker tests from the Service Menu, I can confirm that the "real" diagnostics commands work just fine and sounds could be heard during both tests.
Please follow the steps below and see if manually running the diagnostics commands via the "Service Menu" produces different results then those provided by the Sony Support app.
1. Turn your volume up!
2. Dial *#*#7378423#*#*
3. Select "Service tests"
4. Select "Speaker" and listen for sound
5. Select "Earphone", then place the phone to your ear and listen for sound
If steps 4 & 5 play a sound, rest assured that your hardware is functioning just fine and a replacement WILL NOT BE NEEDED. If you are still unable to hear anything then keep on reading as the solution for me was literally nothing more then changing my ringtone back to a default tone.
There was only one variable that made sense here which was that I had changed my ringtone to a custom file stored on my SD card just before restarting my phone after the first test. So instead of assuming it was hardware related, right from the start my assumption was that the Sony Support app has a bug and could not properly link to ringtones that are stored outside of the default system location. I was able to verify this by changing my ringtone back to the default tone and re-running the Sony diagnostics and confirming that both tests produced sound just fine. Now if you still cannot get sound then I would suggest contacting Sony support to inquire further. If a replacement is actually needed, they will let you know.
Now...with regards to the rushed suggestion to replace your device...I feel I must comment towards such a ridiculously rushed conclusion...
Simply put, it's not right to send people on a wild goose chase without first taking the time to test things out for yourself... even a tiny lil itsty bit? Personally, I know I'd be pissed right off if I found out that I sent in my phone without there actually being a problem with it, and whether you realized it or not,, that is actually the least of the potential consequences? You really should have considered that some people might have to pay to ship it, and others might have to drive an hour or two to get to the nearest repair centre? So maybe...just maybe...even the simplest of suggestions like "restart your phone" or "ask google!", prior to suggesting that someone should replace it, would have proven to be infinitely more useful? I hate to be rude, and I get that you were just trying to help, but if you don't want to spend any time at all to test anything out for yourself, then maybe it is best to not comment on the issue in the first place? Just simply let them wait for someone who is...
This is just my two cents, but I firmly believe that no advice is better then bad advice...
EDIT:
Model: XA2 Ultra (H3223)
Build: 50.1.A.13.83 (Stock Rom)
Sony Support Version: 4.2.10
So I found 2 other issue with Sony's diagnostics tests.
1. When you run the wifi test it will pass, but it will leave your wifi disabled afterwards and it will not allow it to be turned back on until the phone is restarted. Manual testing worked just fine.
2. When you run the ambient light test, the image provided by Sony will show, but it will already be faded while under normal light conditions. It will work while under a bright light, but it does not function correctly under normal conditions. Manual testing works just fine.