Google Navigation Map not aligning properly... - Droid X Themes and Apps

I'm not sure when it happened - but after the latest update to Maps I noticed that when I use the (Google) Navigation app the arrow direction does not align to my direction of travel but instead maintains a "North is up" alignment.
previously hitting the blue arrow would result in the screen aligning such that the direction of travel would be "up".
to confirm, I used the Google Navigation app on my Dad's Incredible and found that his behaves as mine used to - that is the direction of travel (arrow) becomes "up" by default - or whenever the blue arrow is pressed.
I seem to remember that my Navigation has been like this for a few months now - it *definitely* was *not* like this for the first 9 months or so I used the phone as a navigation device!
I have tried calibrating the compass - but no joy.
this is more than just a small annoyance - since the phone *always* shows the map oriented as North being "up", then even tho the direction displayed is technically correct it is VERY easy to go the wrong way...
for example: just now I told the phone I want to go to an address directly West of my location - as I'm sitting here I have the top of my phone pointing approx due west and it's showing that direction as "North" and displaying an arrow for the direction I want to go - West - as 90° to the right of North... which is correct BUT if you just look at the arrow it LOOKS like it's telling you to turn right - which would take me South!!
does any one know what's going on here?
Note: I am currently running Apex 1.4.1 on Froyo 2.2.1 (kernel 2.6.32.9.**) but had the same exact problem while running Liberty 1.5

Related

JF1.41 Bug? changes the way the touchscreen works?

On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Well, maybe you should go back to an unrooted phone so that you can play with your steamy window....
LPChris, I would expect a little more maturity from a "senior member"
I am trying to contribute to make JF the best it can be. Maybe your just having a bad night or something, but theres no need to be so childish.
:ed:
Looking through your posts it seems like your just having a bad night
Back on topic:
While this may be a stupid little problem with one application. Should finger-area sensitive applications continue to be made this could isolate JF1.41 from the market. Naturally I dont care much for steamy window, but I would like to prevent other issues in more... useful... applications
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
sjbayer3 said:
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Click to expand...
Click to collapse
Ditto about LPChris lol, a lot of his posts sound like that, but yeah I noticed the same thing about the steamy window app before and after using JF 1.41.
Steamy window, LOL! sorry guys. anyway keep up the great work.
Yes, this is a trivial example, but it does identify a real issue.
I was reading through the various google android groups last night and I ran into some info that seems to addresses this issue. From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
your Steamy Window app seems to make use of the size value as it was originally designed. Now with the change, with only one finger input, this value is set to some minimum, producing a thin line.
To test this theory, see if when you touch the screen with two fingers the size of the mark gets bigger.
Why can't a capability bit or other mechanism be defined that could be used to indicate whether or not an application were multi-touch aware, so that the touch handling behavior at the lower levels would revert to "standard" behavior for normal (non-multi-touch) apps? Trying to make the multi-touch hack fully backwards compatible may not be practical.
I tested your idea about multituch possibly fixing steamy window
My only results are really strange.
If I touch with two fingers it will make a line about the width of my 2 fingers, but its located in the top left, no matter where my fingers actually are. Furthermore the line isnt straight its curved.
Now, after my first touch, it seems if I touch it again it just crashes.
ex-MN said:
From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
Click to expand...
Click to collapse
Edit: Hmm... the x-y data of the second finger is stored in separate fields. I think the usage of the size field is just as a boolean to tell multitouch capable programs that second finger data is being sent.
themes and JF RC versions. be careful
TheDudeOfLife said:
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
Click to expand...
Click to collapse
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
BhanG
bhang said:
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
Click to expand...
Click to collapse
After some more testing I have this same issue on 2 1.41 compatible themes (rusty metal and fade to blue) I am going to go back to themeless 1.41 but I think it is more related to the multitouch 'hack' than the theme themselves. I find it hard to believe that a bunch of icons could mess this up. I watches my screen jitter between the left and right screen for 3 minutes today before I just performed a soft reset on my phone.
Note: I also applied each theme from a fresh flash of 1.41...not on top of each other.
this happens with screen crack also, but it doesnt affect me that much until i start not being able to select stuff. i know it may be important its just not to me... yet *knocks on wood*
Yeah Ive noticed it too..
I thought that it was just the app at first.
I might be switching back to .31 then at least til this gets fixed.
Steamy window def is NOT reading my fingers location or size properly.
I've also seen it affect touch paint found in the API Demos. Doesn't even register touch anymore.
It appears multi-touch is premature at this point and to implement multi-touch throughout the OS and not just the browser like everyone seems to think isnt good. It is definitely is throughout the OS and probably will affect any application that uses the second touch value to register touch size.
My other concern is that dev's won't take this hacked multi-touch into account so they will continue to write programs that won't be compatible since its not the "norm"
Taken from and android forum...this is my biggest concern
"Please think about soft keyboards when considering multi-touch APIs,
where the problem isn't detecting the distance between two finger, but
rather is allowing a 2nd finger (or thumb) to come down on a 2nd key
before the first finger (or thumb) has been released. The proposed
API to provide only a centroid and the distance between fingers won't
work at all for this sort of application.
I think you'd ultimately want to package this as additional
GestureDetector subclasses, depending on whether the type of gesture
detection wanted was pinch/zoom or multiple/overlapping taps.
Keyboards (and maybe games) would use one class, browsers another.
Providing the right information from a touch panel to drive either
detector might be challenging, especially if the panel provides
'unpaired' x and y coordinates rather than individual touch locations,
but I believe it could be done. "
JesusFreke,
Any thoughts on this?
Yeah lets hear what JF's got to say.
I originally thought that the multitouch was embedded in the browser, It's too soon to have it throughout the entire OS...
How about 1.41=with multitouch and 1.42=without
I've installed JF1.41 and I have an unusual bug....sometimes the screen behaves like it isn't calibrated..i press the screen on a button and it is pressed another one....have anyone encoutered this problem?
I invite everyone to do the following to find out how ur touch registers on ur screen. Open anycut. Get it if u don't have it.
Click activity and find raw image viewer. Click ok and then click on the shortcut.
Now start moving your finger around and see the results.
Let's all post our results here so we can figure this out.
Post in the same format as me:
ROM: JF1.41
1 finger - it surpisingly followed my finger perfectly. It only registered the very center point of my finger.
2 fingers - it appears that it made the same point as the 1 finger, however now the point was exactly in between my fingers and stayed there as I moved them around.
Ok so now we need ppl with stock rc30 and 1.31 so we can test this out!
You wanna have some real fun? Try it with 3 or 4 fingers.. It goes nuts..

[Q] Issues with standard android apps & games on Xoom - Any Solutions?

Hello,
I have noticed on certain standard android apps a number of issues that I have come across. I have tried with auto-rotation on and off of screen in settings. I have restarted my Xoom also. I don't have any of these issues with any of the tablet apps.
1. First off Jetcar Stunts, and Return Zero the menus are normal and function fine, but when you go into a race the screen looks like it is tilted at 45 degree angle. If you turn your Xoom vertical, the screen will level out, but you are looking at the car on the left side of the screen.
2. Several racing games TurboFly 3d and couple of others I cant think off of the top of my head work fine and the screen is in the right position, but to when you tilt to the left it turns the car to right, and vise verse the other way. The turning controls have been switched.
3. Adao File Manager, Adao Uninstaller, ishoot, and Medieval Castle retain their original size of an android phone. Is there any way to zoom in or have these apps stretched to fit the screen? The ipad lets you view iphone apps standard size and stretched size.
Anybody experiencing these problems, or have any solutions?
Thank you for your input.
DensoYamaha41 said:
Hello,
I have noticed on certain standard android apps a number of issues that I have come across. I have tried with auto-rotation on and off of screen in settings. I have restarted my Xoom also. I don't have any of these issues with any of the tablet apps.
1. First off Jetcar Stunts, and Return Zero the menus are normal and function fine, but when you go into a race the screen looks like it is tilted at 45 degree angle. If you turn your Xoom vertical, the screen will level out, but you are looking at the car on the left side of the screen.
2. Several racing games TurboFly 3d and couple of others I cant think off of the top of my head work fine and the screen is in the right position, but to when you tilt to the left it turns the car to right, and vise verse the other way. The turning controls have been switched.
3. Adao File Manager, Adao Uninstaller, ishoot, and Medieval Castle retain their original size of an android phone. Is there any way to zoom in or have these apps stretched to fit the screen? The ipad lets you view iphone apps standard size and stretched size.
Anybody experiencing these problems, or have any solutions?
Thank you for your input.
Click to expand...
Click to collapse
Install "Spare Parts" free from the market.. Open it and uncheck the box for compatibility mode... Might not fix every issue as some things just refuse to run on HoneyComb yet but it should fix some of them. It will absolutely fix your last section where the apps don't fill the screen.
The problem is not you, or anything you did. The issue is honeycomb. Not all apps are compatable yet. It was like trying to run a win xp app on win 7 when it first dropped. Didnt work. Just wait. They will be updated eventually.
Thank you,
The spare parts helped with the apps that was stuck in their native resolution. It now fills the whole screen.
Yep... I'm waiting, too... seems Napster, SiriusXM, and my banks' apps aren't even showing up as installable on my Xoom - but they all show up on my Pure running XDAndroid! (waiting for July so I can upgrade to a real Android phone ).
I immediately put this all down to the fact that Honeycomb is so new, the devs didn't have opportunity to build versions compatible with it... yet.
But... this begs a question... I'd love to be able to copy the .apk's from apps I directly-installed on my XDAndroid port, onto the Xoom and see if they'll run anyway... but I can't seem to find the apk's. Being a noob on Android still, can anyone tell me how I can get a hold of these app files, or does the Market simply download, install, and delete?
Thanks...
~ BereanPK

I9003 Compass Jumping Around!

Well the compass does point at the right direction but when I fired up street view and turned on compass mode, (which is pretty sweet btw) no matter how still I hold the phone or even place it flat on a table for that matter, the image keeps quivering. The image just does not stay in one place! Went into test mode and under sensors I checked it out it was the same quivering. Also under settings>display> theres an option for Horizontal calibration, funny thing is even when placed on a absolutely flat surface (I tried at different places), the small ball in the center does not stay still! Why is this so? This issue makes using sky map,street view,layar etc quite unusable because of all the jitter! Any fix for this?
Jumping around happens when you are near a magnetic field such as speaker,computer etc. move away in open area, jumping should reduce.
In the compass settings> noise filter set to strong, sensor rate slowest & buffer display ticket with green check mark.
This should solve your problem, if not then report back.
sgsI9003 said:
Jumping around happens when you are near a magnetic field such as speaker,computer etc. move away in open area, jumping should reduce.
In the compass settings> noise filter set to strong, sensor rate slowest & buffer display ticket with green check mark.
This should solve your problem, if not then report back.
Click to expand...
Click to collapse
Which compass settings are you referring to? Where do I find these settings?
Compass is a app which you can download from the market in that you will have those settings, once set you wont face that jumping issue. Mine stay still.
By saying street view are you referring to layar which shows a compass too?
Ok I'll try that out, but will changing those settings in the app apply to the whole system?
The street view I was referring to is from google maps with compass mode on.
I had the same problem as your since i installed compass & set it the right way that problem was never noticed, earlier it use to jump, so my best guess is that those settings are somehow being read by other apps too.
In my case google maps with compass mode remains quite still.
Do report back with the results.
Well I tried your fix and it worked kinda, the twitching has reduced but its still there which is very annoying. In service test under sensors it still keeps jumping around. I've also tried using it in a place free from magnetic signals but still the same. Is it this way for all galaxy s users our could mine be faulty?
Mine stays perfectly still (FW ddkb1) whats your FW?
Compass on google map works only when gps is enabled & locked, if gps is not able to lock then it might have the problem which you are describing.
Are you able to lock on to the gps (icon stops flashing)?
Well I'm on the same firmware as you (kb1). (kies keeps crashing if I try to update to kb2, but that's another issue)
The twitching issue I'm talking about should not be related to gps, on the map itself it does not twitch at all, but when I go to say new york on the map and go to street view, and enable compass mode, even if I hold the phone vedas still the image on the screen still vibrates.
I tried to replicate at my end but i don't have any issues, maps don't vibrate, however they rotate as per compass pointing (locked) to north.
What do you mean by street view, there is no such option in maps at my end, when i go to new york I see a road map only, is there something which i am missing?
Seems some setting we have is different between you & me though we both are on kb1 but cant figure out what.
sgsI9003 said:
I tried to replicate at my end but i don't have any issues, maps don't vibrate, however they rotate as per compass pointing (locked) to north.
What do you mean by street view, there is no such option in maps at my end, when i go to new york I see a road map only, is there something which i am missing?
Seems some setting we have is different between you & me though we both are on kb1 but cant figure out what.
Click to expand...
Click to collapse
Ok so i'm guessing you have never tried street view before, ok so just enter 'new york' into the search box and it will take you there, once there you will see a big red arrow pointing downwards to the map with New York written above. Click on the name and select the right most option (a man standing) that will take you to street view, once in there press the menu key and turn on compass mode. Try holding the phone still or even place it flat on a table and see if the image twitches. (Its a pretty cool thing anyways, you'll enjoy it! )
The probelm that I am facing is similar to this
Jumping Compass
Oh I have seen street view on desktop numerous time didn't know its a feature on our phones too. Now I tested street view as per your instruction & it does change its angle 5° approx & flicker but in compass mode it just show me the bottom of the 360° image & no more moves.
The issue could be in street view as its in beta testing.
The jumping compass video is what I was having the problem but after I changed the settings it got stabilized.
We can ask bala who has updated his fw to kb3 to test this if the problem is same or not.
sgsI9003 said:
Oh I have seen street view on desktop numerous time didn't know its a feature on our phones too. Now I tested street view as per your instruction & it does change its angle 5° approx & flicker but in compass mode it just show me the bottom of the 360° image & no more moves.
The issue could be in street view as its in beta testing.
The jumping compass video is what I was having the problem but after I changed the settings it got stabilized.
We can ask bala who has updated his fw to kb3 to test this if the problem is same or not.
Click to expand...
Click to collapse
Have you updated your google maps? Its at version 5.3.0 now. It could not be street view's fault because it used to work perfectly fine on my xperia x10 earlier. Come to think of it the x10 had far better gps and compass components (but seriously lacked in other areas).
Changing the settings in compass app worked only in that app itself, its not a general fix for it though.I would like to know if all i9000/i9003 have this problem...
magnetometergate?
I just bought this same phone and I'm experiencing the same jitter. This is a real show stopper since it renders useless apps like those mentioned here, panorama stitching, Google sky map and others. I'm really annoyed and thinking about returning the phone.
The Iphone 3Gs does not suffer this issue, the compass moves smooth and softly.
This seems to be a hardware problem, maybe Samsung can improve the software filter or update the sensor firmware.
Since I am using xxkb3 now I tested again but this compass jumping problem still is the same.
I remember that xxkb3 offers few calibration & tweaking of setting for compass but what these settings do is not known to us hence I have not changed anything, I still feel that this can be addressed by tweaking the settings & not really a hardware issue.
The compass in i9003 is more sensitive to magnetic field disturbance hence the problem.

[q] android notifications bar

I am having problems with the swipe down Notification bar on my Desire HD. I would have posted it in there, but this is a general problem, as I have seen it on several android phones in other forums. However, the ones I have seen are all HTC. Whether this is a manufacturer related issue I do not know.
Put quite simply; it won't slide down in portrait. But when I switch to landscape it works perfectly fine.
One of the suggestions was to use Draw Pad and see if there were any deadspots on the touchscreen. So I go nuts, and find a bar about half an inch on the top of the screen that isn't responding, unless I flick upwards quite quickly. But it's not a deadspot, as when I'm using that part of the phone in landscape it works perfectly. I can also swipe down in landscape from the corner (top right) perfect as well. So I would say it can't be the hardware.
The last time the notification bar worked was when I was in Tweetdeck, and swiped like mad through a load of tweets to class them as 'Read'. I've since uninstalled Tweetdeck, restarted my phone (both by using Restart and by removing the battery), and returned the phone to Factory Settings, but nothing works.
I understand that I can install a ROM as a last resort, but I am pretty sure that there must be an app that can reset the touchscreen calibration or something similar, to reset the dimensions of the screen when it's in portrait, or a hidden setting that can reset it. My phone isn't rooted, so I would much rather fix the problem, rather than overwrite it to save the extra work when I wouldn't really appreciate a rooted phone with a custom ROM.
I am running Android 2.3.3 with HTC Sense 2.1. My Kernel Version is 2.6.35.10-gd2564fb | htc-kernel(at symbol)and18-2 #1. The build number is 2.50.405.2 CL87995 release-keys.
(The (at symbol) is because I am new and outside links are forbidden for new users)
My phone isn't rooted, however I am not averse to doing so if it helps solve the problem. I have minimal experience with the Terminal, however, so if it is required, I could do with instructions rather than 'do X and Y'.
Thanks, and sorry for the wall of text.

Google navigation doesn't rotate map when navigating anymore?

Is it just me or does google navigation not rotate the map with you depending on your direction anymore? I have been on IC since august and I had it working like that up until a week or two ago. I can't remember if it was on 225 sse or a previous version where I last saw it working where it rotated the map. I've been on 255 for about a week and when I use navigation it keeps the map stationary with north always north and I can't figure out how to get it to follow my direction as if its looking forward again on the road...thanks for any help!
Sent from my HTC Sensation 4G using xda premium
I thought it was the updates to the EVO that caused that. But the compass was clearly fixed, but navigator didn't work. So it's definitely a software thing, and not related to the phone, I think.
I have same problem
until i see compass icon (top right) and click it

Categories

Resources