Am I the only one that has problem with Photosphere and the gyroscope?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah I got that too. Annoying as f**k.
Screwed up my ppl picture when I was in sphere mode. All upside down.
Anyways it's not final yet so yeah. But still I hate it.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
Same problem, using the final Takju OTA - I never get a single lock-on; the point keeps drifting and at best I get one of the three lock light flashing. Given that even the help pages focus on the new Nexus 4, 7 and 10, I'm guessing we'd have to wait for the next point release to get this working.
People have been reporting success with Galaxy S 3, but not the Samsung I9000, so it's probably hardware-related, or at the very least driver-related
I have the gyroscope drifting off a bit on the first shot, subsequent shots are fine though.
Interestingly, I did a factory reset before 4.2 and it fixed the gyro issue! I can't seem to recreate the fix though. :/
Factory reset didn't help me... Seems my gyro is not only drifting, but its slow too. Hopefully Google fixes this =\
Factory reset didn't help me either -- I actually did a full reinstall from the Takju 4.1.2 factory image, because I didn't want to wait until the Yakju update, and then immediately updated to 4.2 via OTA before doing anything else beyond the initial setup.
A similar problem reported against CyanogenMod suggests that it might be due to the specific gyroscope make (the bug was not for the SGN, though). Installing Phone Tools now so I can check my gyroscope there.
No problem out here
Sent from my Galaxy Nexus using xda premium
Saturday I went to Venice (Italy) and the photosphere was working fine there, now I'm back in Avellino (Italy) and is it not working again.. :/
That's weird..
It was working for me well the other day as well... Perhaps magnetic interference?
sent from my mini tractor
I ended up flashing directly to 4.2 with a full wipe, and I have had non of the problems you describe. (Or any of the other problems people have had with 4.2).
I have however experienced while doing a photo sphere that the gyroscope isn't completely accurate. Meaning that if I go back and fourth a double of times on the first pictures, the next dot will be way of and the final sphere will be missing a part at this point and have an overlap at the end.
Related
Hello, I've got a weird error that I don't even know how to begin tracking down. Not sure if this is an ICS issue, an app issue, or a device (hardware) issue.
Several times now, I get a problem were, after a reboot, all the text on my home screen - names for apps and text within widgets is mangled somehow. Like pixels inverted, or boxed over, etc. (see screenshot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first couple of times this happened, a single reboot made it go away. However with my latest occurrence, I've rebooted several times without a fix.
EDIT: It seems like my data connection may also require examination? Since on the 3rd or 4th reboot I was in my office with a solid WiFi connection (versus previous reboots I was in my car en-route), the problem has now gone away again.
My initial reboot this morning was as a quick-fix attempt at an absent data connection. Guess I'm off to research these "radios" everyone keeps on about...
EDIT 2: Ok, perhaps ignore the above. After a reboot made this go away, it has now come back spontaneously (i.e. just noticed it sitting in the cradle with the error again - no reboot this time.) CRUUUUD.
Are you using a custom Kernel? Some 'Overclock' the GPU to 512MHz, while Stock is 384MHz. Some devices can't handle the increase and cause screen artifacts. Post your Kernel details and I'm sure someone will point you in the direction of another Kernel if this is the case.
Not that I know of - should be all stock, since I haven't rooted or unlocked anything yet (just got the phone a couple of weeks ago).
Thanks for the help.
Stock launcher? Or using nova/apex etc?
Sent from my Galaxy Nexus using XDA
Hi,
Another thread...:http://forum.xda-developers.com/showthread.php?t=1646985
Nothing related to GPU overclock...just about this possibility...
Looking in different threads in Q&A/General.
If you are using the stock launcher...I think I saw a topic with this weird issue with the stock launcher...but I can not find it anymore
In any case clear data/cache of your current launcher,reboot and see...If you're on another launcher than stock,reinstall...
I speak only for the launcher issue.
Yep, stock launcher. Thanks for the other thread.
Seems to be at bay now. Will keep an eye on it.
I've encountered something on my VZW Galaxy Nexus that appears completely new to me. I did some online research but found no one with similar problems.
To give a little background, I encountered this problem after I hit the "traffic to home" Google Now tile which took me to Google Maps. After hitting this tile, though, the graphics for traffic on my Google Maps has become very low resolution. Normally, you see two lines on each freeway, one in each direction. Right now, those lines are all blurry and overlap to the point where I can't see both lanes. It looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I zoom in enough, I can get it to look like it normally does, but zooming out slightly makes it go right back to fuzzy-garbage-traffic:
Anybody know what happened? I uninstalled and reinstalled Maps, but it didn't help.
I'm experiencing a similar issue on my Galaxy Note II on AT&T. I just noticed it yesterday. And it was after I flashed my phone to Cleanrom 4.7. If I zoom in closer, the lines become sharp and are no longer blurry. Not sure how to fix it.
Getting the same thing on my EVO on Sprint. It appears that people have started taking to posting comments in the Play store as well:
https://play.google.com/store/apps/...DEsImNvbS5nb29nbGUuYW5kcm9pZC5hcHBzLm1hcHMiXQ..
I went a step further and reported it using the "Feedback" option in the map.
subhumanderelict said:
Getting the same thing on my EVO on Sprint. It appears that people have started taking to posting comments in the Play store as well:
https://play.google.com/store/apps/...DEsImNvbS5nb29nbGUuYW5kcm9pZC5hcHBzLm1hcHMiXQ..
I went a step further and reported it using the "Feedback" option in the map.
Click to expand...
Click to collapse
I'm getting this too on my Galaxy Note on CM10.1. I think this happened after the last update. Hope they fix it soon. Very annoying?
christran12 said:
I'm getting this too on my Galaxy Note on CM10.1. I think this happened after the last update. Hope they fix it soon. Very annoying?
Click to expand...
Click to collapse
Wiped and updated to the latest nightly of CM10.1 and the problem is gone.
TL;DR - Camera firmware updated on Google Edition, largely unusable since. Any fixes?
Here's the tale. My camera was excellent for the past year or so, and served me well no matter what ROM was being used. One fateful day, I was going to share something to a friend on Google+ while using the Google Play Edition ROM (really very excellent) when I was presented with this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I didn't think much of it, but let it sit while it did this. I eventually came back to the phone after several minutes, only to find the message still there.
I killed Google+ and opened my camera. I was presented the same message that the camera firmware was updating and to wait. I let it sit for about half an hour. I tried again only to receive the same message. Eventually I was presented a black screen with the camera controls, and was able to switch to the front camera. However, the back camera was still only a black screen. I restarted and had the same issue.
I reflashed to a stock based ROM (Insane) and was presented with the same issue, only this time no warning about firmware upgrades in progress - just black screen on the rear camera. At this point I decided an ODIN would probably take me back to where I needed to be, so I ODIN'ed a stock image. The issue was still persistent, but the camera would work every once in awhile now. It was a very rare occasion, but sometimes the back camera would flicker into life and allow me to take pictures as usual. Infuriatingly enough, the first time it started working was when I was trying to show a friend of mine, also into Android, the issue.
Non-TW based ROMs do not work with the rear camera now. The front camera is still working, and sometimes allows videos to be taken.
TW based ROMs rarely work with the rear camera now. The front camera is still working, and sometimes allows videos to be taken.
Does anyone have any ideas on remedies for this issue? Is there a stock Samsung Galaxy S4 camera firmware flashable? I've searched around, and decided to yield to the higher XDA powers of knowledge after no returns.
This is the first phone I've had problems with Google Maps. For some reason it's zoomed out following my route there is no say to get it closer. Ive cleared cache and data of the app. No joy. Can't think what else. Making navigation hard as can't seem to follow the route properly. Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC 10 using Tapatalk
Hey, not an HTC 10 owner (galaxy s7 edge) but my google maps navigation just started doing the same thing today, it's a complete pain in the ass. Guess it's an app problem rather than your phone!
Maybe google play services has updated something and broken it!
Likewise on my LG Ultimate II, since yesterday.
I've found that the zoom-out issue only occurs when the phone is tilted (wide rather than tall), and only when "Tilt Map" is checked in the Navigation Settings. Unfortunately, that's precisely how I prefer to use it.
Hmm glad I'm not the only 1 then. Thought it was my new HTC10 being the problem.
DarthOps said:
Hey, not an HTC 10 owner (galaxy s7 edge) but my google maps navigation just started doing the same thing today, it's a complete pain in the ass. Guess it's an app problem rather than your phone!
Maybe google play services has updated something and broken it!
Click to expand...
Click to collapse
I'm guessing it was some update which has screwed with it. Which is REALLY annoying!
allenw01234 said:
Likewise on my LG Ultimate II, since yesterday.
I've found that the zoom-out issue only occurs when the phone is tilted (wide rather than tall), and only when "Tilt Map" is checked in the Navigation Settings. Unfortunately, that's precisely how I prefer to use it.
Click to expand...
Click to collapse
I've already tried turning tilt off and on messing around with options doesn't make any difference. I always have my phone in landscape while driving. Haven't had chance to try in portrait.
I have noticed though if I'm on a long stretch of road it zooms right out then when I'm approaching hing a turning it does zoom in Abit more. But it's a stupid function.
Sent from my HTC 10 using Tapatalk
Same here Sony Z3c, Send feedback to Google via the app, they obviously farked it up on the last update. I thought it was stuck in 2D mode, but its just zoomed out very far.
I note that as you get to junctions etc it does zoom in briefly, but then zooms out again afterwards.
Hey fellow OP5T owners,
I recently upgraded to BluSpark r106 (probably completely unrelated) on OOS 5.0.4 and today I noticed that my cam has a weird bug on the bottom of freshly taken pictures when holding the camera vertically (stock cam).
It does NOT happen when I am holding it horizontally, and sometimes it doesn't occur when you switch to the gallery fast enough after taking the photo.
It also does NOT happen in portrait mode at all, but when I'm holding it vertically in Pro mode and in normal auto Picture mode.
Video is not affected in any way.
To me, it looks like the processing of the picture gets messed up because the pictures come out fine in the gallery after taking the photo, and after a very short timespan, the artifacts pop up in the final picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm assuming you're using the standard, unmodified camera app that comes with OOS. If that's the case I would suggest you download any of the third party camera apps that are available in the Play Store and see if you can replicate the same problem. If the problem does not appear on another camera app, then it's almost 100% likely that is a software issue related to the camera app and the kernel might be a possible culprit.
If that's the case in your case I would wipe dalvik/cache and flash stock kernel and see if the issue is resolved.
Same issue with third party camera apps like Open Camera and the Nokia Cam that floated around here somewhere.
I'm now dirty flashing stock OOS 5.0.4, then check if it solves the problem and then go back to modifications.
Thanks for your input!
Edit: I tried it out twice now, both time same results, the issue is solved with a dirty flash of OOS 5.0.4 and Magisk, and is replicatable by flashing BluSpark r106.
It seems to interfere with the cam, especially when using touch to focus.
Same here. Thank you for your post! I was worried that it was hardware related.