Hello everyone, does anyone here have shaky or wobbly compass and gyroscope function? For me this is most noticeable while using apps like Google Sky Maps, Street View, GPS Status, and more. Vertical panning while using Sky Maps and Street View is not smooth and zigs and zags back and forth horizontally. The compass is also shaky and sometimes can be inaccurate by up to 45 degrees!
I first noticed this problem on my first et4g that I got back in December, and with that phone the problem persisted through different roms, including the GB versions of MIJJz BLEND, Calkulin's, and Blazers, and ICS versions of MIJJz BLEND and Calkulin's.
After that phone died (didn't power on at all, no led, no charging, nothing) and got it replaced from Sprint, I kept my new phone on EL29 stock. The problem is the shaky and wobbly motions are still here! At first I just thought it was my first phone's hardware, but after getting my second phone, I am wondering if all et4g's have this issue. Even my HTC Hero (that thing still fully works and is awesome) is smooth like butter and is accurate. any ideas?
Also, I did not root my second et4g (might as well wait for OTA ICS), and did not test to see if it is solved on the AOSP and AOKP roms.
Related
http://forum.xda-developers.com/showthread.php?t=742081
so happy
direct link: http://www.kwaak3arena.com/
Thanks, i was playing normal kwaak3 without on screen controller using volume buttons to go straight and back that sucked ;D
Sent from my GT-I9000 using XDA App
i finally got it installed properly in my phone, the speed is FREAKING AMAZING!!!!!!!!!
it puts any computer to shame
1.It works a tad better on eclair than froyo.
2.When running kwaak close other apps for best performance.
3.Best setting - wide screen res, 16bit depth, everything else to max.
~60 fps.
It doesn't put any computer to shame
from present time that is
still..
i was comparing it to the CPU of the time when the game was released
Ahh... sorr to bump an old thread guys.. figure its better then starting a new one.
Ive been running kwaak3arena 0.2 for several weeks now without issue, but the other day it seemed to stop working properly. main issues are that the brightness of the textures seems to have increased, the controlls have been muddled up, and the application crashes sometimes in some levels. This all came on unexpectedly after running flawlessly for ~2 months!. The only thing i can think of is that after i used the application with it working perfectly, i had downloaded the XE.com app, and after that it starts screwing up. Im also noticing, though not sure if its just me, that other areas of the phone are running very slightly more laggier / choppier then they were before.. i think.
I have tried uninstalling and reinstalling kwaak3arena, as well as getting rid of the xe.com application, but still no fix.
Phone is basically standard running voodoo lagfix.
Anyone else having similar issues?
I also noticed that the developer has released a new version which he's charging for
edit: Also, for symptoms, ive noticed ive been renamed "unnamedplayer," from GalaxyS
Seems like since gingerbread leaks dropped, we have had camera issues plauge our beloved evos. I am currently on mik g and have only suffered 2 rebooted. One w stock 4.53 kernel and now once w freedom. Great kernels and great roms but my real question is anyone w the 4.53 ota having any reboots using the camera?
Since it isn't all the time, its not a major deal...yet...but it can be frustrating taking family pics and I have to say ****! My bad ass rooted partitioned class 10 extended battery Evo just froze taking a picture. :-(
I've had issues with my OG Evo (hw 0004) rebooting occasionally after taking a picture. It's probably happened a dozen times or so.
I'm running stock because my evo happens to be plagued with the error not writing bad block when trying to run revolutionary. Also, half the time when the phone does reboot, it loads with the original factory wallpaper instead of what I had it set to. Figured these were all related somehow.
Personally I've decided to live with it for a couple more months and get the Epic 4g touch when my upgrade is available.
Mine when it reboots the brightness will jump to full brightness when before the reboot its set to auto. I'm testing the bliss 3.5 camera which seems very quick in comparison. If it does it again I will disable auto brightness and keep in testing. There has to be a reason the whole system is stable and the camera dumps.
Panning and rotate aren't working at all. They just stopped working recently and panning force closes when I try to test it.
Sent from my Epic 4G Touch on Calc's GB ROM
I had the same problem. Dropped the phone from 2 feet and it would take forever to go to landscape and never go back to portrait. I flashed a ROM that morning before work and didn't get a chance to test anything till after the drop. I thought it was the ROM so I flashed a stock ROM and the problem persisted. So I flashed like 5 different ROMs and the problem persisted, then I realized that the gyro or accelerometer broke that day I dropped it. I downloaded an app to read sensor data, tried it on a couple of GB and ICS ROMs and the accel and gyro readings were always screwy. The funny thing is that when I took it to sprint they thought they were going to fix it with a factory reset. The guy came back out 10 minutes later confident it was fixed and the problem persisted. He didn't know that I had done extensive testing to find the root of the problem. Take it in let them do whatever they do then get a new one from warranty.
Thanks it managed to fix itself. Panning doesn't work still, but getting it replaced would be more trouble for me than for them for something I don't even like.
Has anyone else had issues getting Panorama to work clearly using the stock camera app on Jelly Bean 4.1.1? Over the last week, Panorama has been recording garbled images on two of my devices. I don't believe it has anything to do with the ROMs, but may have been due to one of the Gapps updates from Google Play.
I have 2 GSM Galaxy Nexus phones. One running AndroidME 1.9 Stock Google, the other running AndroidME 1.3 AOSP Light. Both versions run the included kernals and basebands, only the AOSP Light version was flashed with a version of GAPPS allowing for Picasa syncing. Taking panorama photos worked perfectly on both prior to this last week. Movies and regular photos work fine.
I haven't read any issues online similar to mine as of yet.
Thanks.
I have a sporadic issue with panoramas where it won't start capturing. You hit the button, start panning across the scene, and it just won't capture. Sometimes it'll do this over and over several times. Haven't really found a way to replicate it, seems random.
I've been having the same problem.. just noticed it starting about 4-5 days ago. Have been trying to find others experiencing the same thing..glad to see you both are, not so glad that there is a problem though.
BUMP
No one else experiencing this??
Try reflashing the ROM over what you have. I have never heard about this problem before. I believe camera is part of the ROM not gapps.
I'm stock...not rooted... received Jelly Bean OTA on Friday, but actually noticed the issue with my panorama a few hours before it came (hadn't used it for a week or 2 before that so don't know exactly when it started)
Just posted in this thread because it is the only place I could find anyone reporting similar issues...
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?