Database Users

Screen sometimes turns white while using camera.....

hi.....everyone
i have a problem on my 8125....when i use the camera to take pictures .. after sometime the screen turns white and will not give it up for some time....does anyone knows why is this happening......do suggest some tricks and tips to solve this problem......thanks in advance

battery status...
Are you by any chance overclocking your wizard?

no....i have not over clocked....the clock speed is 185 mhz

For me, when I wake up my phone, sometimes the camera program randomly turns on. I don't know why.

this issues is happening all the time...when ever the phone goes into power saving mode...the camera screen turns white...i wont be able to take pictures....it will take couple of minutes to return to the original screen...or in some cases a soft reset is the only solution ...

i have same situation when phone rings - still cannot find out what is a reason - rom change is not working...
i am using bs, but machine is not overclocked.

HARDWARE?
If the problem exists with different operating system builds I would have to think it is a hardware issue. Unless of course on each build you implement the same third party application in which case the Software could be causing it....What type of software do you run? What is running in memory normally? This is what i would be looking at.

i am running XM6r5.... the memory is normal and i am able to many applications simultaneously....as soon as the screen turns while....when i hold it against a object for sometime....the screen gains some colorness and turns to normal...i didn't have this problem with the ROMs that i used earlier...i guess this requires some fix....

[Q] Faulty Compass

I just bought my first droid: a wildfire.
I wanted to run orbot (TOR) deperately so I rooted the device the second day after I got it... (using rEVOked)
Well orbot didn't work but I didn't care that much since I had already found many interesting app to play with. I was generally pleased by android. It is by far the best OS i've tried on a mobile. I does what I expect it to do even though I had never used it before.
At some point I noticed that my compass was useless... I could find some specific headings where pointing it less than 5 degrees to the left would turn the shown heading by 180 degrees.
So I though it just needed calibration. I tried all possible ways found on the internet to come to this strange results:
1. Calibrating the compass with the fast 8-like motion would almost fix the compass. It wasn't perfect though. For example turning it 180 degrees would change the heading 185 degrees. I has also found a 90 degree turn which changed the displayed heading by 100 degrees, even after a calibration, which is pretty inaccurate for augmented reality apps like layar (which btw rocks).
2. Even after the calibration, just closing the compass app and reopening it would result in the compass being completelly uncalibrated. For example I placed the compass on my table over the edge, perfectly aligned. It shows 255 before the calibration, 265 after the calibration, 255 again after restarting the app. When I say "app" I mean ANY app that uses the compass, from google maps (which don't show arithmetic heading of course) to Super Compass and Wigle.
I then decided to return my phone back to the shop (I bought the device without any plan) but I read that rooting probably voided the warranty. I still don't understand WHY people argue about rooting voiding or not the warranty when they haven't tried it. I've never read about a single HTC user that tried to return the mobile and it being rejected by HTC because of rooting. Has anybody got personal experience about that matter????????
In deperation I restored my mobile to factory defaults. After the reset, the compass was almost perfect. Only minor mistakes like +-4 degrees over a 180 degree turn. After 2 days the compass is again useless. WHY??? Why doesn't it store the calibration data? Why HTC neglected to check the compass before releasing the phone? And why do they consider rooting harmful to hardware? Is there even a slight chance that rooting messed my compass up?
What do you suggest I do? Is there a way to unroot the phone and return it for service? Will installing the 2.2 update take me back into the warranty?
I have a second Wildfire with exactly the same firmware as mine. It's not mine but I can take it for a few days, so, is there a way to transfer the firmware from it to mine? (because it's a Greek firmware, which I haven't find the "unrooting wildfire" thread)
I accept condolences, advice, tips, donation or whatever you've got for me.
Please guys, I need your advice here. I really don't want to keep the phone in this condition...

Accelerometer Calibration, Sensor Error, Game Control, Google Sky Maps

First noticed a problem using Google Sky Maps. I couldn't tilt phone to view above the horizon. I was on a 2.2 ROM, but I never tried it on a stock ROM. This position sensor error would effect any app that uses the phones position (pitch, roll, azimuth) as an input, for instance game control. It would manifest as not being able to turn or climb. It also effects horizontal/vertical screen switching.
What I know from testing:
A. Download Sensor Debug from market. The simple program lists the sensor values that are reported to programs: Azimuth, Pitch, Roll, as well as force sensed along X,Y and Z axis. If the system is working properly, values with the phone sitting still would read: Pitch 0, Roll 0, X and Y Forces = almost zero, Z (gravity)= -9.xx. Tilting the phone to the left or right, Roll goes +/- 90. When tilted toward the sky, pitch would smoothly increment from 0 to -90 when vertical, and -180 when upside down. My phone when sitting on the table will read (depending on calibration method): Pitch= 0 or -180, Roll =0, Z axis= either +9 or -9. Rolling the phone is sometimes limited to +/-30 degrees. Pitch increments in the proper direction, but is capped. If I start at 0 when flat, it stops at 90 degrees when vertical. If it starts at -180, it stops at -150.
B. Calibration settings appear to be stored in /data/system/ms3c_yamaha.cfg. Changes are real time. If deleted, it is recreated. Values vary greatly. Settings/display/horizontal calibrate effects the values. There is also a calibration utility available from terminal: su system/bin/sensorcalibutil_yamaha. The terminal method has been reported as more accurate.
C. The problem has persisted with full data wipes, factory resets and ODIN return to stock.
So, is anyone else seeing these kind of problems. Questions:
1. What kind of pitch/roll values do you see in Sensor Debug:
2. What are the values in your /data/system/ms3c_yamaha.cfg? and what kind of calibration did you do if any?
3. I want try going back to stock 18 again, but think my method is not complete. What is the most thorough method?
I used the method described in the "my gps fix for 2.2" thread: http://forum.xda-developers.com/showthread.php?t=869806. It uses Odin 1.3 and SPH-D700-DI18-8Gb-REL.tar.md5.
There's another "Return to Stock" thread http://forum.xda-developers.com/showthread.php?t=773032. It uses the same version of Odin and SPH-D700-DG27-8Gb-REL.tar, and maybe a different PIT. Not sure what a PIT file is.
It appears that the threads re ODIN for DK28 use a different version of ODIN and or PIT, or no PIT.
4. Is it possible that ODIN isn't writing part of the firmware? If I can verify the problem after a thorough return to stock, well maybe it is a hardware issue and I'll just go down to Sprint and get a new one!
Hey thanks for listening! So looking forward to fixing this issue and appreciate any and all help/comments. Thanks!

I've had the same exact problems that you're having. I've done the same things you've done to try and fix the problem but nothing works. I've really only noticed the problem in sky maps because I haven't played any games that required going above the horizon. Hopefully someone can figure out a fix for this because I'd really like to use sky maps again.

I used the link above, return to stock, last page of that thred. Odin3 ver 1.67, and DI 18 stock with no PIT. Sensor debug values are the same....
What are your sensor debug values? Maybe try the su calibrate if u can.
Went to Sprint store. Nominal debug values on an Epic and an Intrepid...
Not a tech store so walking 1 mi to the other one. I am resolveed that I have hardware issues, or at least issues that ODIN can't fix.
I don't have insurance, but it's only 3 months old...should be covered?

Make a big scene, ask for manager... they may try to refer you to sammy warranty... don't put up with it. But the 7 bux a month is def worth it...

I don't think that the problem is the hardware. Sky maps was working for me before flashing over to the froyo roms. I'm just hoping that once the official froyo is released, it'll be fixed with that.

Update of my journeys....
2 mi walk to the tech store. 45 min later, they say yes the accelerometers are faulty, you need a new phone. Don't know what they did, but the only two things not stock on the phone where Google Sky and Sensor Debug.
So great, I get a new phone! But wait.... "it'll be here in a week." But I don't live in San Francisco, so that does me no good. They say to talk to go to my local store in SC, or call CS to get it mailed. Evidently they won't swap with a retail phone.
CS is no help. Won't authorize a retail swap. Won't have replacement sent to residence or my local store. I'll try calling them tomorrow.
In the meantime, I'm going to ODIN 1.6.1 straight to SPH-D700-DK28-8g-rel.tar.md5 OFFICIAL with no PIT, one click root, and restore my Bonsai system and data. My previous 2.2 upgrades have all been via update zip from DI 18.
So I guess the question remains, does the phone have hardware issues, or did my 2.2 upgrade dork something up that ODIN can't fix. Seems like it will be a while till I can Google Sky....

You cannot use another person's accelerometer values. Each and every accelerometer is different and calibrating will give everyone different values.
To fix the accelerometer you can run the following command in a terminal emulator :
Code:
su
/system/bin/sensorcalibutil_yamaha
The problem is that something has changed from Eclair to Froyo that Samsung hasn't taken into consideration. The update from a DI18 stock to the OTA Froyo should work without a hitch.
Hopefully w/ the official Froyo update we will get a fix. Otherwise, we should confer w/ noobnl or the CMSGS team to figure out how they were able to resolve the issue.

I've used the utility numerous times. Agreed that individual accelerometers would be somewhat different, but I think the differences wouldn't be very large in the .cfg file. The utility is "fine" calibration.
My device has gross errors.... Z axis prior to running the utility is +9.xx instead of -9.xx, and lay flat pitch is -179. The utility helps a little, but pitch values are referenced wrong, and don't increment properly even after running it.
Obviously there are areas of the phone that don't get reset with ODIN return to stock (Phone remembers the time, account info, etc). Sprint Tech couldn't get the g-sensors working right either with what ever reset procedure they use. Either data is stored on a level ODIN can't reach, or it's hardware failure.

Im a complete noob so correct me if I am imagining this... I had the same problem and fllashed back from froyo. Did the su/system/bin/sensorcalibutil_yamaha fix and it worked. Started restoring all my stuff and the orientation started to dog again.
I messed around and tried changing my launchers. I was using ADW and switched back to TW and the response was much better. I changed to Launcherpro and it is a little slower but not as bad as ADW. Am I high? Please forgive my noobiness.

I have noticed the same problem. The D18 rom was fine and all the games worked good. I checked the horizontal calibration and the sensors seem fine but the games and sky map don't seem to register properly with 2.2. I'm waiting for the OTA to come out b4 I take the phone back for a swap.

I'm actually having the exact problems you all are having with the pitch sensor, ever since I moved to DK28. Right now it is annoying, but I am hoping it will be resolved when DL11 is released. If not, it looks like I'll have to call Sprint and have them get me a new phone, because some programs don't work correctly right now.
Sent from my SPH-D700 using XDA App

I noticed this problem while using maps, my compass seemed to have East and West swapped (but North and South were fine). I used the calibration tool in the Settings menu under "Display" (horizontal calibration), but I put the phone on the table upside down (hanging off the edge enough for the "calibrate" button to be in reach).
Not ony did this fix my compass, it seems to have improved the auto rotation response time dramatically
Sent from my SPH-D700 using XDA App

styles420 said:
I noticed this problem while using maps, my compass seemed to have East and West swapped (but North and South were fine). I used the calibration tool in the Settings menu under "Display" (horizontal calibration), but I put the phone on the table upside down (hanging off the edge enough for the "calibrate" button to be in reach).
Not ony did this fix my compass, it seems to have improved the auto rotation response time dramatically
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Wow...that seemed to help a ton. The games are off, but I don't really play them anymore so no issue. Sky map actually works now. The auto rotation is much better also. Thanks.
Edit: This fix works. I also started my game prior to doing the fix paused it and did the calibration. The game works great now.

styles420 said:
I noticed this problem while using maps, my compass seemed to have East and West swapped (but North and South were fine). I used the calibration tool in the Settings menu under "Display" (horizontal calibration), but I put the phone on the table upside down (hanging off the edge enough for the "calibrate" button to be in reach).
Not ony did this fix my compass, it seems to have improved the auto rotation response time dramatically
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks! This seems to have fixed problem. I'm not exactly sure which part fixed it for me so I'll just go through what I did. I placed my phone face down and did the calibration in display settings, but then my phone wasn't switching to the correct orientation, so I rebooted my phone to see if that would help. It didn't. So I then did the terminal emulator calibration and now it's fixed. So, that makes me wonder if it has something to do with the calibration utility in display settings having some settings that are flipped around.

Woah... that worked. For whatever reason, it actually worked. Hmm...
Sent from my SPH-D700 using XDA App

Wow!
I actually tried the upside down trick once before with out success. Thought I had some results this time... then added another step. Voilla!
1. Working on a rooted froyo ROM. Upside down horizontal calibration from system/display/settings/display.
2. Reboot. (Not sure if that step is needed)
3. Connectbot su system/bin/sensorcalibutil_yamaha
At this point, sensor debug showed no success. Pitch and roll both limited to 30 deg.
4. Settings/display/autorotate. Uncheck.
Back in sensor debug, every thing checked out.
Anyone think it's still fixed if you enable autorotate?
Sent from my SPH-D700 using XDA App

I agree that the calibration in display settings seems to be the problem, sensorcalibutil works fine right-side-up. But sensorcalibutil didn't seem to fix the orientation lag, so it's possible that the display settings' calibration is correct, the internal compass I installed upside down, and sensorcalibutil has been modified to compensate... but I doubt it, the hardware should work no matter what the orientation, so a software problem in the settings' calibration is more likely the cause
Sent from my SPH-D700 using XDA App

I've tried everything in this thread and I still can't get google sky maps to tilt up, above the horizon. Anyone word on EB13 resolving this particular issue?
no matter what i do, pitch is never a positive value in sensordebug..

same with sky maps. only other problem i'm having after calibration with the exception of an occasional compass jitter

I also have a problem with Sky Maps.. Pointing up will not register.

[Q] Acer Orientation Sensor

My Acer works just fine for orientation sensor games, like asphalt, need for speed, etc. However, when I use things like ilighter, ibeer, etc the orientation is very off. The application is supposed to be help in portrait mode to be considered upright. However, when I want to use the program, I actually have to hold it in landscape (a 90 degree turn counter clockwise ) to actually have the program register that it is "upright". I originally thought that this was a problem with the program, but there are a number of programs that act this way. It acts this way regardless of orientation lock on/off or any settings, and only impacts on some applications.
Is this a common issue on the tablet device due to honeycomb issues, or is it something wrong with the sensor?
Anyone having similar issues?
Thanks in advance.

This is probably due to the different Android versions we use.
I have noticed the same issue on some apps that were made for my phone running Froyo (2.2). The app works fine on my phone and it reverses every sensor on my tablet so it becomes useless. The app you're trying to use is probably not made to support the tablet hence the sensor problems.

Ive been testing this out with other things. like bubble level, flight games, labrynth, etc. ever application is off. It seems to be seeing the x and y axises as being different. x=y y=x etc.
Anyone able to try downloading ilightr or ibeer or bubble or some other setup and seeing if they have the same issue or not, please?

phoenixbennu said:
It seems to be seeing the x and y axises as being different. x=y y=x etc.
Click to expand...
Click to collapse
exactly the same here...tested with ibeer, bubble, turbofly 3d.
i don't know if it's the same problem with a 3.1 version. i've tested all the apps with 3.2

Gyroscope issue on nexus 7

Has anyone had any issues with the gyroscope? Is there anyway to recalibrate it?
When playing games I notice it veers to the left, for example temple run on a flat surface, character is running along left wall. I guess this could be an app issue.
Anyone else experience this?
Thanks

Does it use the accelerometer at all? If so, completely close the app, hold the tablet in the perfect "Centered" position, and re-launch. This will re-calibrate the app to the accelerometer.

I get an issue in Modern Combat 3 were within about a minute of play the character ends up looking at the ceiling very annoying. Tried recalibrating in app etc. but to no avail. Anybody else experiencing this?

Similar issue, I have to hold my device completely straight up before the screen rotates. Problem with the gyroscope maybe? But when I play games like Rip Tide GP, it works perfectly, senses every single movement, no matter how slight. I'd hate to have to return it, since this unit has no other issues .

flexwong said:
Similar issue, I have to hold my device completely straight up before the screen rotates. Problem with the gyroscope maybe? But when I play games like Rip Tide GP, it works perfectly, senses every single movement, no matter how slight. I'd hate to have to return it, since this unit has no other issues .
Click to expand...
Click to collapse
I'm having the same issue!
Everything works fine except the screen rotation, which I have to hold the device completely vertical (or toward me) to make it rotates.
In games, it seems to work fine though.
I have no other issues, and would hate to return it back too.
Is there anything we can do to calibrate this?

satanicsurferz said:
I'm having the same issue!
Everything works fine except the screen rotation, which I have to hold the device completely vertical (or toward me) to make it rotates.
In games, it seems to work fine though.
I have no other issues, and would hate to return it back too.
Is there anything we can do to calibrate this?
Click to expand...
Click to collapse
Ditto here.
My case with stand sits at angle of 15-20 and when a new app is launched it fails to detect that it should be in Landscape mode?
Here's a demo of the issue:
http://www.youtube.com/watch?v=IIYzn54uN9Y

I had to recalibrate my compass to make it work right. There are instructions on youtube -- open an app that uses compass, etc. and spin it three times around on three different axes.
Don't know why, but some apps seem to have compass issues when others do not.

BaronInkjet said:
I had to recalibrate my compass to make it work right. There are instructions on youtube -- open an app that uses compass, etc. and spin it three times around on three different axes.
Don't know why, but some apps seem to have compass issues when others do not.
Click to expand...
Click to collapse
But it's not a compass issue. I downloaded a compass app for my N7, it works perfectly. Just can't get the screen to rotate unless it's held at a perfectly vertical angle.

I don't know if this is just me, but I'm so used to just kinda giving the device a little shake to point the gyro in the right direction (for landscape or portrait), so I haven't noticed anything weird.

flexwong said:
Similar issue, I have to hold my device completely straight up before the screen rotates. Problem with the gyroscope maybe? But when I play games like Rip Tide GP, it works perfectly, senses every single movement, no matter how slight. I'd hate to have to return it, since this unit has no other issues .
Click to expand...
Click to collapse
I also have this. I've gotten used to the fact that I need to just quickly hold ot vertical. On a positive, I find my phone is too sensitive, and when I lay it flat on the table it sometimes switches orientation when I don't want it to, but obviously my Nexus 7 does not have this 'issue'.

I'd say mine rotates automatically at anything beyond say 30-40' from horizontal and while very slowly tilting it to that angle. I definitely do not have to bring it to anything near 90' for this to happen. I am not sure that I'd call it not rotating at 15-20' an issue other than one of sensitivity, and if it becomes overly sensitive it has a tendency to flip at the smallest movement/vibration, which occurs in a number of phones on different roms.

if anyone else is still having this problem I figured out how to fix it. Close the app/ game, then restart with tablet flat on a table or surface. That should reset it at center.

I have been having this problem since day 1. In temple run if i hold my nexus straight he runs down the right wall, i have to hold it about 25-30 degrees to the left to center it. Other games and apps exhibit the same problem. I have yet to find a solution. I have tried all the tips suggested here and even flashed back to stock. No luck yet.

I had an issue where the gyroscope endlessly turns towards one direction. Going to erase the tablet and see if that fixes the issue. Will report soon.
--update
erase and reset resolved the issue for me

I got my new one today (already have one with bad screen) and it has this problem.
Have to hold the tab directly facing me to rotate, games veering off to the right etc.
Calibrating with compass makes everything work until I remove it, then all screwed up again.
Been on to Google for a replacement

i'm developing a 3d augmented reality app and i tried it on my nexus 7 and after a few other apps that i tried that use the gyro it looks like google swapped the x and y axis or something. so it's not really a hardware error, but more on the software side...
edit: or maybe not. but there's definitely something going on with the gyro.
edit2: on further research it seems that the timestamp of the gyroscope sensor is broken, somehow i end up always getting the same timestamp. on my other android devices (galaxy nexus and galaxy s 2) this is not the case. if this is true (and my findings are correct) then this is definitely a bug that needs to be filed to google. can some other developer confirm this?

Hi,
I just started having this problem :crying: :crying: very sad with it.
It worked perfect since I received it a few days ago, then I locked (on the top bar) to use in an app and after I unlocked it it stopped working.
The behavior/test goes as follows:
- on the home screen, click on Chrome (or any other app that is supposed to rotate freely)
- turn landscape CCW, the app turns
- turn it back to portrait, the app does not turn
- back to home screen, open the app again
- opens in portrait
- turn landscape CW, the app goes landscape but upside-down (to be viewed as if it was turned CCW)
- tries rotating the app, it doesn't ever rotate again.
I would hate having to return it, but if it stays like that, I don't have other option.
------
edit:
I've just checked for games that uses the gyro:
Temple Run: the character is always on the right-hand side of the screen.
Highway Rider: although it's possible to turn the moto left, if I center the screen it will go to the right hand side

that's it,
just gave back to Carphone Warehouse (UK) and now I have to patiently wait for them to receive a new one so I can go pick it up.
I installed this https://play.google.com/store/apps/details?id=imoblife.androidsensorbox app that left me without any questions that the accelerometer was not working horizontally on the screen (if you holding in portrait) :crying:
let's just hope that the replacement doesn't have any of the faults that we've been reading around the forum.

I found a "workaround". I installed the "Compass" application from Google Play and use the "Calibrate" option... and it solved the problem.
However, I need to re-do the same steps when I shut down and start my tablet again.
That's the best I found so far...

There is an app called GPS Status & Toolbox https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2&feature=search_result
It has a calibration tool and I had to run it a few times but once it got things working, it did stay that way even after shutting down the Nexus 7.
It even stayed that way after removing the app altogether but after altering the DPI to try tablet mode, it knocked the gyro off again so had to reinstall the app.
Such things really are just workarounds though and I certainly wouldn't consider keeping the device and having to keep messing like that.
Fortunately, my replacement has a perfectly working gyro.