Related
I just got Captivate and I really enjoy the phone, but I'm having an issues with all applications that use digital compass (Compass, Google Sky Map, Layar, etc.). All of them are very jumpy. If I open up Google Sky Map, stand still and slowly turn, the map is jumping every few seconds, it doesn't smoothly rotate with me. I just compared it to my broser's Evo and it's like night and day. His phone is rotating the map very smoothly with no visible jumps, and on mine you can clearly notice jumps all the time. Is this happening to everyone, or my phone just have defective digital compass? Or is this an accelerometer issue all together?
Am I the only one having this issue? Should I go exchange my phone then?
I think the compass is wonky on all Captivates, and maybe all Galaxy S phones. We're hoping for a software update to fix it.
Ya I am also having this problem. I have tryed out some racing games and some other games that are not playable. I have downloaded some of the sensor test apps and they jump all over the place. Sky maps is also the same. It seems to be the magnetic sensor and the 6 axis. I don't see them using a cheap sensor and then hyping it in the ads and on the box. I am thinking it probibly a software issue as none of the other phones had this type of sensor.
Sent from my SAMSUNG-SGH-I897 using XDA App
Am I the only one not having problems then? Well at least on the compass I am not, have tried any accelerometer games
Edit: My accelerometer is fine also, it seems to me a good way to check is a game like Labyrinth Lite that is solely the accelerometer for control, and that game is very playable which it wouldn't be with the problems you guys are having...
My Compass works perfectly, any gyro or accelerometer based game works perfectly, it's only Google Sky that seems to be a bit jumpy. And it doesn't jump "all over the place," rather it just is jittery while it is being moved about. However I noticed the same jitteriness on my friend's Droid, so it may just be a problem with Google Sky in general.
asrrin29 said:
My Compass works perfectly, any gyro or accelerometer based game works perfectly, it's only Google Sky that seems to be a bit jumpy. And it doesn't jump "all over the place," rather it just is jittery while it is being moved about. However I noticed the same jitteriness on my friend's Droid, so it may just be a problem with Google Sky in general.
Click to expand...
Click to collapse
I just tried google sky on my captivate and it also is jerky like yours. Is your friend's droid the first moto droid? About a month ago, I was looking at my sister's moto droid (1st gen) and google sky worked perfectly.
asrrin29 said:
My Compass works perfectly, any gyro or accelerometer based game works perfectly, it's only Google Sky that seems to be a bit jumpy. And it doesn't jump "all over the place," rather it just is jittery while it is being moved about. However I noticed the same jitteriness on my friend's Droid, so it may just be a problem with Google Sky in general.
Click to expand...
Click to collapse
Google Sky Map doesn't jump all over the place for me, it also just jittery (when you move slowly), but Layar does. So does the Compass app... It becomes a bit better if you run any of the accelerometer test apps in the background, but even then it's a bit jumpy... Hoping for a software fix for this some time in the future.
Similar issues
I own a Captivate, and I am a serious astronomy buff and was very excited to try out google sky. but when I tried it out I discovered it was very jumpy when I used it casually indoors during the day. But I was far more disappointed at night. When I tried it then, I started up the program and noticed it was jumpy like before but figured I would just have to live with it. But when I pointed it up at a constellation, I noticed the stars didn't match, and a nice circle labeled "sun" that clearly wasn't there. It wasn't reading the correct position apparently. This problem makes Google Sky almost entirely useless, which is incredibly disappointing.
What makes it worse is my roommate who showed me a similar program on his iPhone 4 that was completely smooth and accurate. Boy did that make me feel like I had the inferior product.
I have also had issues with the jerky compass, and seemingly anything else that deals with the physical position of the phone. For example, the phone on google maps showed me as moving around (seemingly in a path) while I was sitting down, not moving; and the GPS accuracy in general seems fairly low (usually 50-100 ft off-ish).
If these problems can be fixed via software update then I would be MUCH happier with my phone once things worked as well as I would think they are supposed to.
This is particularly important to me also because I am looking to start developing android apps and would want to use and then test apps using these systems. As of right now though, these seem to be far below par.
-TheOnlyMerlin
The compass didn't ever work for me either, would point in random directions and hop all over. Layar was unusable and Yelp's Monacle would never show things in the right direction. Skymap was just a mess.
I just thought the games that you had to tilt the thing sucked, like labyrinth, racing games, etc. Couldn't control any of them.
The two things on the phone I loved were the screen and swype.
hobbbbit said:
Google Sky Map doesn't jump all over the place for me, it also just jittery (when you move slowly), but Layar does. So does the Compass app... It becomes a bit better if you run any of the accelerometer test apps in the background, but even then it's a bit jumpy... Hoping for a software fix for this some time in the future.
Click to expand...
Click to collapse
I just update Google Earth on my captivate and if I use hardware sensors to control the view, it uses compass to update your view on Google earth and it seems (at least for me) very smooth in comparison to Layar or Google Skymap.
what I've noticed with mine:
mine was jerky as mentioned above.
a simple compass app shows that if I tilt the phone the compass follows, which tells me the app is using the tilt sensors and not the compass.
I flashed jh2 and it worked for a while, but at some point it stopped again. still trying to narrow down why... but this tells me it's a software thing
I'm not sure if it was an app I installed, or maybe it worked until I turned the phone off, not sure, need to do more research, really just hoping our froyo update will fix it
I have the issue too. When you go into the test app even with the phone sitting on a table the compass heading is constantly changing. Its an issue with all captivates.
I was a vibrant owner and had the same issues. To my knowledge, this problem is evident in all US galaxy s phones. The epic may have avoided the bug due to its later release. Samsung is supposedly pushing out a fix for the GPS and we're all hoping they will address the totally laggy compass too. There are YouTube videos demonstrating the problem on the vibrant. Cross your fingers but know you're not alone.
I've certainly noticed this problem too with the compass. The six-axis seems fine though.
Mostly I've found that how you hold the phone effects the interference with the compass. I've done a side by side comparison with a real high quality compass (both phone and compass calibrated to magnetic north) and the Captivate isn't all that bad after it's "settled" and on a level non-metallic surface. It's just the quick movement or change of direction that really seems to throw it off.
Hey all - I don't mean to bring this long dead thread back to life, but I figured it was better than starting a new one.
Has anyone figured anything out with the jittery compass issues?
I've only had my Captivate for a week, but am definitely dealing w/ the jitters (let alone the GPS issue).
I've found that it can be demonstrated pretty well using the sensor test on the phone (*#0*# -> Sensor) - it displays the data from the magnetic sensor... on mine, X, Y, and Z coordinates are all bouncing up and down within a couple of points.
Any thoughts or advice on this?
I'm still well within the first 30 days.
yourtvlies said:
Hey all - I don't mean to bring this long dead thread back to life, but I figured it was better than starting a new one.
Has anyone figured anything out with the jittery compass issues?
I've only had my Captivate for a week, but am definitely dealing w/ the jitters (let alone the GPS issue).
I've found that it can be demonstrated pretty well using the sensor test on the phone (*#0*# -> Sensor) - it displays the data from the magnetic sensor... on mine, X, Y, and Z coordinates are all bouncing up and down within a couple of points.
Any thoughts or advice on this?
I'm still well within the first 30 days.
Click to expand...
Click to collapse
Did you update to JH7 yet? I heard it fixed the compass issue.
gtg465x said:
Did you update to JH7 yet? I heard it fixed the compass issue.
Click to expand...
Click to collapse
Indeed I did - I had the opportunity to briefly examine another unit, as well and while I believe it was on JH6, the compass seemed very steady.
Sorry for the bump- but I have a more specific question for people:
Does anyone have a unit where the compass is steady? Either in the sensor test (*#0*#) or elsewhere?
Sent from my SAMSUNG-SGH-I897 using XDA App
yourtvlies said:
Sorry for the bump- but I have a more specific question for people:
Does anyone have a unit where the compass is steady? Either in the sensor test (*#0*#) or elsewhere?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If i put it on a flat surface away from any metal then it is almost solid. Some minor movements and now and then. But it is super picky about being near anything metal.
is anyone using wiimote for playing snes and psx games? if so how do you get it to work? i have the emulators and games installed, i have wiimote installed and bluetooth on. the wiimote is connected within the wiimote app but then when i exit the app it no longer does anything. i just can't get the controller to work in the game.
edit: figured it out, just had to map the keys within the emulator/game
Based on the lack of responses, my guess is gtablet users are not too much of gamers... Also the fact that there are not too many "past a few day" Gtablet owners
I could not get the Wiimote app to see my Wiimote. Bluetooth was on, of course. No fun retro gaming this device was born to provide, it seems. The v-pad for games is too awkward due to display size, device weight and response of the tablet in the corners (where the controls are- is not very responsive).
I was pumped due to the performance, but you are right that controls are not too good..... Need Wiimote to work. I naturally figured it would work, but given some of the other issues, I may be assuming too much.
I probably will return the Gtablet this weekend and wait for a refurb. $400 is too much with screwed up sensor and controller functions not working via blutetooth. $300 is more of a compromise
I get the impression NOTHING was tested on this device. Nothing appears to really work other than USB sticks and even those can not be hotswapped. "USB" must have some other meaning for the OEM of this device.
Even USB keyboards and mice work with the Archos devices. All this power constrained by pi55poor FW.
on zpad the wiimote works great, i got a usb keyboard working too. i really wish someone smarter than me could figure out how we can select other keyboards. anybody?
Crimton said:
on zpad the wiimote works great, i got a usb keyboard working too. i really wish someone smarter than me could figure out how we can select other keyboards. anybody?
Click to expand...
Click to collapse
You're not using TnT 2.0 then (or did they used to work?)? I have tried USB devices with no luck. Ditto on bluetooth input control devices.
You think the keyboard is the root cause for failure on Gtablet in TnT based roms?
I can not even get the Gtablet to see the Wiimote, yet alone map it to work.
rushless said:
You're not using TnT 2.0 then (or did they used to work?)? I have tried USB devices with no luck. Ditto on bluetooth input control devices.
You think the keyboard is the root cause for failure on Gtablet in TnT based roms?
I can not even get the Gtablet to see the Wiimote, yet alone map it to work.
Click to expand...
Click to collapse
usb keyboard worked for me on tnt lite 1.0.2(i'm poretty sure theres a small chance it was zpad). on tnt i can install wiimote, the app will see the wiimote but i can't choose wiimote as my default input because tnt will stay on the tnt stock keyboard. so if there were just a way to choose another keyboard as default it'd be all good. this guy found where the problem may be http://forum.xda-developers.com/showpost.php?p=9394102&postcount=3.
Crimton said:
usb keyboard worked for me on tnt lite 1.0.2(i'm poretty sure theres a small chance it was zpad). on tnt i can install wiimote, the app will see the wiimote but i can't choose wiimote as my default input because tnt will stay on the tnt stock keyboard. so if there were just a way to choose another keyboard as default it'd be all good. this guy found where the problem may be http://forum.xda-developers.com/showpost.php?p=9394102&postcount=3.
Click to expand...
Click to collapse
Makes sense, but I can not even get the device to see my Wiimote. Looks like the permission issue will impact other control efforts as well.
rushless said:
Makes sense, but I can not even get the device to see my Wiimote. Looks like the permission issue will impact other control efforts as well.
Click to expand...
Click to collapse
i would stay on zpad but i get uids inconsistent message everytime i reboot. it seems real laggy sometimes too. but i love how it is more similar to my incredible than the tnt interface.
I have the same problem with tnt lite
it sees the wiimote
the buttons work
but I can not change the keyboard input so I cant use it either
I have problems with my device - the screen completely stops responding.. im going to take it in and exchange it.. possibly get a refund.. Im not impressed with this.. everytime I run youtube.com it forces the browser closed..
not happy about the market place not displaying all the apps either tons of apps on the market place I use on my phone that dont work / wont install on this device.
Crimton said:
on zpad the wiimote works great, i got a usb keyboard working too. i really wish someone smarter than me could figure out how we can select other keyboards. anybody?
Click to expand...
Click to collapse
A huge reason for this device is old school gaming. No wiimote- no keep (At full price. Better gamble if will get fixed by paying less money).
Seems a fair analogy is the Gtablet has a Ferrari engine, but no tires (laggy UI).... or steering wheel (accelerometer flucked' up), or lights (LCD appears to be mounted upside down due to bad viewing angles).
I could throw in more car analogies about USB and blue tooth issues, but already a rough ride.
After installing zpad it is getting better. I have the device tweeked to the point I like it.. gotta factory restore right now though to get an exchange because of the screen.. one that is done though I think I,can really get used to this.. gotta get flash working though..
rushless said:
A huge reason for this device is old school gaming. No wiimote- no keep (At full price. Better gamble if will get fixed by paying less money).
Seems a fair analogy is the Gtablet has a Ferrari engine, but no tires (laggy UI).... or steering wheel (accelerometer flucked' up), or lights (LCD appears to be mounted upside down due to bad viewing angles).
I could throw in more car analogies about USB and blue tooth issues, but already a rough ride.
Click to expand...
Click to collapse
i agree as far as playing games. the on screen controls are a joke to actually be competitive in a game. wiimote makes playing old nes or psx game MUCH more enjoyable. i'm thinking this has become a deal breaker for me...
Crimton said:
i agree as far as playing games. the on screen controls are a joke to actually be competitive in a game. wiimote makes playing old nes or psx game MUCH more enjoyable. i'm thinking this has become a deal breaker for me...
Click to expand...
Click to collapse
I am going to return mine and get another one with the 60 day holiday return policy. That way, plenty of time to see if a fix is provided and more vulture time for a refurb- While still able to use the G for other stuff
Who knows, the 101 may be better than expected with 2.2........ VS better fix the frickin' bluetooth function on the Gtablet!
There is a way to get the Wiimote activated on TnT Lite - it would require replacing the Settings.apk from the zPad, Nvidia dev kit or even the Vega.
But, there are issues. The ones I've noticed is that the new Settings.apk cannot change the brightness controls, and that new widgets cannot be created on the homescreen after the change - and this is why I leave the TnT Settings.apk in the Lite Build.
roebeet said:
There is a way to get the Wiimote activated on TnT Lite - it would require replacing the Settings.apk from the zPad, Nvidia dev kit or even the Vega.
But, there are issues. The ones I've noticed is that the new Settings.apk cannot change the brightness controls, and that new widgets cannot be created on the homescreen after the change - and this is why I leave the TnT Settings.apk in the Lite Build.
Click to expand...
Click to collapse
Catch 22
Returned my G yesterday. I will get another one with the 60 day return window for holiday purchases... and hopefully a refurb to boot
Need a controller to work or this device for me is a comic reader and web surfer. The Archos 101 will cover that and games.... just not PSX too well, but at least controllers work with the 101.
Perhaps we will see a stable FW build where everything works (not CM)- including things broken by Viewsonic's apparently semi-clueless OEM dev team.
I like how the Gtablet maps apps (that force data to microsd) to go the internal space, so that frees up the microsd for other things. Seems Archos has corrected the app space issue on their Gen 8s, but may have went from one extreme to another. They may have mapped ALL of the 8gb and 16gb for apps. This would mean a lot of wasted space, since 3gb is about max needed fro apps, since all larger apps force data to the microsd anyways.
If Archos mapped as reported, there is about 4.5gb wasted space on the 8gb and 12.5 on the 16gb. Ironic- that they may have gone from one extreme to another. Droid X maps this way too. Wasted space.
I was having problems while playing asphalt 8, the triggers don't work if I mash them down for gas, but if I pump them, or go just before full throttle, them the car would go, buttons work normally in other games, but the gas trigger seems defective, have you guys had he same problem?, I starting to think this might be a hardware issue, and not a software issue, but if you guys are having the same issue, please post it here !
After much messing about we have Modern Combat 5 & MOGA controller working with limited lag. The secret is to remove any additional helper apps you have installed for the Moga, remove the controller from Pivot and resync as B MODE.
Then start Modern Combat 5 and set your Sensitivity to 100% and Aim Sensitivity to 75% (Thanks bradleyg5 for the settings)
It's not perfect but it's considerably better than A mode and is close to playable with only a slight slugish feeling, also gone is the Iron site bug which is great and makes it much more playable.
androidizen said:
After much messing about we have Modern Combat 5 & MOGA controller working with limited lag. The secret is to remove any additional helper apps you have installed for the Moga, remove the controller from Pivot and resync as B MODE.
Then start Modern Combat 5 and set your Sensitivity to 100% and Aim Sensitivity to 75% (Thanks bradleyg5 for the settings)
It's not perfect but it's considerably better than A mode and is close to playable with only a slight slugish feeling, also gone is the Iron site bug which is great and makes it much more playable.
Click to expand...
Click to collapse
It won't work with the pocket, as it has no b mode nor could I even get any input from it in game whatsoever. Just a warning unless someone has a solution. The Pocket seems not to work with MC5.
Archienj7 said:
It won't work with the pocket, as it has no b mode nor could I even get any input from it in game whatsoever. Just a warning unless someone has a solution. The Pocket seems not to work with MC5.
Click to expand...
Click to collapse
You can get it to work with the Universal MOGA Driver. But the problem is that the pocket has only one row of back buttons for example you can't shoot because there is no button on the moga for So we have to wait until a proper support from gameloft comes...
flopower1996 said:
You can get it to work with the Universal MOGA Driver. But the problem is that the pocket has only one row of back buttons for example you can't shoot because there is no button on the moga for So we have to wait until a proper support from gameloft comes...
Click to expand...
Click to collapse
My moga universal driver app crashes when I hit the enable driver button, on my galaxy s5
please take no offense but i feel like your fix is more of a semi functional work around that should be obvious to most people right away
when i saw the game was out, i bought it and immediately began looking for my moga pro. i saw that the phone recognized the moga in "a" mode, but the mc5 app didnt detect it, so i flipped the mode to off and then to "b" and once again the os saw the controller, but this time mc5 recognized the controller and so i was happy until i noticed how slow/low sensitivity was.
i cranked up the sensitivity to 100%, but it still is about 30% too slow for my liking.
a true fix/solution would be to get the controller working whether its in moga's mode, that appears to be loosing support, but this could be slow too, or getting hid mode to work with a acceptable output/input.
i wonder is there is someway to adjust the hid joystick sensitivity. im guessing with 6axis or what ever its called probably works beautifully since its touch emulation with tons of tweaks, realizing that the on screen thumb sticks are fast enough as is.
Thanks worked great
potna said:
please take no offense but i feel like your fix is more of a semi functional work around that should be obvious to most people right away
when i saw the game was out, i bought it and immediately began looking for my moga pro. i saw that the phone recognized the moga in "a" mode, but the mc5 app didnt detect it, so i flipped the mode to off and then to "b" and once again the os saw the controller, but this time mc5 recognized the controller and so i was happy until i noticed how slow/low sensitivity was.
i cranked up the sensitivity to 100%, but it still is about 30% too slow for my liking.
a true fix/solution would be to get the controller working whether its in moga's mode, that appears to be loosing support, but this could be slow too, or getting hid mode to work with a acceptable output/input.
i wonder is there is someway to adjust the hid joystick sensitivity. im guessing with 6axis or what ever its called probably works beautifully since its touch emulation with tons of tweaks, realizing that the on screen thumb sticks are fast enough as is.
Click to expand...
Click to collapse
There is an app for touch emulation. But still not playable It's called Game Controller 2 Touch.
What makes it Unplayable? Seems like mc5 wouldn't even know it's I/O was being spoofed, let alone care?
I'm going to some reading on that app you pointed out. If it works the way I envision it i will be tossing some coin towards the dev. Thanks
Sent from my SM-N900P using xda app-developers app
Still a tad bit laggy. May need to switch to my PS3 controller and use the touch emulation for now.
potna said:
What makes it Unplayable? Seems like mc5 wouldn't even know it's I/O was being spoofed, let alone care?
I'm going to some reading on that app you pointed out. If it works the way I envision it i will be tossing some coin towards the dev. Thanks
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
ok, so i bought the app and i have been messing around with for 3 days and i still dont have it working, the dev points towards 2 issues, one being kernel permissive issues and another problem with knox. i tried 2 of the 3 fixes and i cant get it, but i also dont know what i am doing. i emailed the dev last night so we will see what happens. i will try to report back.
potna said:
ok, so i bought the app and i have been messing around with for 3 days and i still dont have it working, the dev points towards 2 issues, one being kernel permissive issues and another problem with knox. i tried 2 of the 3 fixes and i cant get it, but i also dont know what i am doing. i emailed the dev last night so we will see what happens. i will try to report back.
Click to expand...
Click to collapse
The Six axis app does work pretty well. Not lag in the inputs, but the need for proper HID implementation would be better. Or at least release the updated for A mode on the Moga Pro.
I know the thread is nearly dead but I have a question. Has anyone been able to use touch emulation with MC5 and a MOGA Pro? Every app I've tried won't register touch emu for my MOGA, MC5 just continues registering the controller as input. I want to use touch emu because the sticks are god awful for aiming with such low sensitivity. And yes, ivebgot it set to 100%. Any help please?
How to turn 180 degrees, i am new to this
I have a problem with moga pro wont recognisw my controller it works on the begining you chooae multiplayer and as soon as the game starts ir wont respond its on b mode and the controller works with other emulators so its not a hardware problem does any one know why
So far I've noticed this with two games, Bladeslinger and Granny Smith.
The game loads, but touch input does nothing. These two games work fine with the stock software for my shield (update 4.4), but under Bliss or Dirty Unicorns they don't respond to touch input.
I thought this might be because my GPU or CPU wasn't being detected correctly, so I tried this guide (http://gamin9.blogspot.com/2014/09/how-to-play-tegra-games-on-non-tegra.html) for running Tegra games on a non-Tegra device. Struck out there.
I would appreciate any help with getting these two games working with Bliss on my tablet. It's so much faster overall, and the battery life is better too. I did switch back to stock for a while, but the battery drain wasn't worth being able to play two more games than i could with Bliss. The developers of those games can't help; Bladeslinger's developer doesn't respond to email, and Granny Smith's only offered me a refund. So much for fixing a bug...
I notice Plague Inc has a tendency to freeze under Bliss or DU, which also doesn't happen with stock. Not sure if that's relevant or not.
I just tried flashing the NVIDIA blobs, but it caused too many problems so I had to undo it. Didn't seem to fix these games either.