While driving home I got an idea to remove the lag in Tomtom 7 on the Touch pro by using an optical trick. And I need your advice....
In tomtom you can choose an image as the pointer of your location on the map (by default blue pointer). Some posts in this forum stated that the real position is at the tip of the pointer, where this used to be in the 'center' of the pointer. Still some people have to deal with lag.
Now my idea: what if we change the default icon by a custom made icon of which for example the lower half is transparent, while the upper half is the default pointer. The resolution of the image that represents the icon would be a number of pixels higher (width stays the same) and it would be the questions whether Tomtom allows larger images to be read as icon.
But: assume it works, in your screen the blue pointer would move a but to the top of your screen, like as if it reduces your lag.
Probably there are other complications (like what wil happen during a turn, would it look like your position is outside the road....??), but it is just an idea.
My favorite idea I heard was to have a 5-10 meter pole (or whatever your lag is) mounted to the front of your car with your phone stuck to it and then have a pair of binoculars next to you so you can actually see the screen
But seriously, have you not noticed that when you stop driving the position reported is very close to where you actually are. With your suggestions this would change and IMO not be good.
I resolved my lag issues with my diamond (and I'm sure many others have as well) by using the latest versions of iGO8 and using it in 2D mode. I swear, I have no lag now what so ever. The same can't be said for in Tomtom but TTN7 is rubbish compared to iGO8 anyway IMHO .
GFXboost also apparently improves the visual performance of iGO8, so another point to consider .
Related
Hello all. Fantastic forum and many thanks to all those contributing.
I received my O2 Xda Orbit 2 last week and I'm very pleased with the unit.
I only have two small issues with the device.
The first is more with WM6. As a left hander I would really appreciate being able to place the scroll bars in applications such as IE on the left hand side of the screen so that I don't obscure the screen almost every time I'm reading something. I don't suppose there's much hope of this happening though.
Secondly, I've read with interest the issue regarding the backlight on the keylock screen and I will try the registry tweak to get the backlight to come on at full brightness so that you can see the lock-code keys in daylight.
However, is there any way of making a short cut to adjust the backlight brightness from the 'today' screen? I'm finding that I adjust the backlight brightness for my office/indoors and then when I go outside and use the unit I can barely see the screen and it takes several attempts to get in to the unit and vary the backlight brightness.
It would be lovely if you could say press the central button and then turn the jog wheel clockwise/anti-clockwise to brighten/dim the backlight. Does any bright spark know if there's a means to do this or at least make backlight adjustments simpler?
Same goes for backlight on the Co-pilot software. As it's usually plugged into the car's fag-lighter socket the backlight's on full. Then when you drive at night it blinds you. It would be lovely to be able to press the central button and twirl the wheen to adjust screen brightness. All it actually does is to zoom in/out of the Co-pilot map.
Otherwise, a fantastic unit.
Hello,
First: If you find some software to handle the device easier for left handers please tell me. I'm always interested.
Second: If you install the GPRS Monitor Software (was delivered with my device) it places an slider for backlight on your Today Screen. So you can easily vary the intensity of your backlight.
Maybe not the best solution, but better than nothing.
Hope that helps...
P.S. Do you know a trick to disable the screen, so I can only hear the commandos? (Would be helpful when I go for a walk and get lost in the wood. In most cases I don't have some breadcrumb to mark my way home...)
Hi,
Yes, backlight control isn't all it could be on the orbit2/touch cruise (or any other windows mobile device).
For Copilot if you go into settings / map styles and select "automatic" under day night mode then it does behave better at night.
As for easy control over the backlight - after searching for a few days I noticed that the HTC Home screen that I'd already installed, had a backlight control app on the third tab. Each time you press on the app with your finger it changes the backlight intensity (in 4 stages)
Finally - The bluetooth light was really irritating me whilst the phone was in the car cradle at night. The following link discusses a means of disabling the light.
http://forum.xda-developers.com/showthread.php?t=365892&highlight=bluetooth+light
Backlight adjustment
Thank you for your replies.
I've been experimenting with the HTC home plugin.
I downloaded the version for WM6 that supposedly correctly the backlight adjustment this morning but have discovered that the backlight function does not work on my Orbit 2. Of course, I may be doing something stupid.
May I ask which version you're using and which works with the Orbit 2?
I've also installed the GPRS monitor software but I can't see anywhere where it displays a backlight slider on the today screen.
Many thanks again.
Lom
Backlight and gprs monitor
Sincere apologies,
I just discovered the backlight slider on the notification icon of the gprs monitor. Not the best solution but something.
Many thanks for the suggestion.
Hi, I wonder if there is a possibility to make the TC adjust backlight automatically? I know there's no light sensor, but can't the front-cam be used as one?
What do you think?
Or am I overseeing an already existing tool for this?
Many thx,
Eric
Same idea provided in "development and hacking" but no response!!
I think it would be a great thing
Unfortunately it doesn't seem to interest many people, both of my postings have so far been ignored... It's a pity, because I think it could be done by some pros inhere.
We're all seeing fancy phones with accelerometers that can proudly switch between landscape and portrait modes coming out these day, regardless of whether they have a kb or not. That got me thinking. Why do phones have a portrait mode at all?
A major reason is historical, of course, and the current rational is "it's always been done like that". There was never a landscape candybar phone. I suspect this has something to do with the positioning of an old text-only screen above the keypad.
But now this is no longer applicable with the advent of screens that are also the input method. For some tasks, landscape is clearly superior (watching videos springs to mind). Some favour portraits - notably, some text lists. Others are completely orientation-agnostic (like home screens).
Physically, holding a device horizontally is no harder that doing go vertically and the thumb can easily reach all parts of regular-size phones' screens. Landscape orientations can be additionally used double-handed.
So far, the match is "even", but still, portrait seems to hold a dominant position. As we use our devices more for media (which prefers landscape) and text-input (same, via a physical or virtual keyboard). I do think, when using my phones, that more can be done sensibly in a landscape mode. Landscape screens also approximate our computer monitors more closely, which may make future convergence easier.
Any thoughts about how the future of mobile screen orientations will go?
I only use landscape mode on my phone for video since the top and bottom bars eat up too much real estate in that mode.
orientation can be changed under settings
and even if it don't keep it after a soft-reset
it would be pretty easy to make a program
which put it back to landscape
but many programs would not be compatible
and as stated no real benefit apart from video
and games being as most devices buttons are laid out
I only use landscape mode on my phone for video since the top and bottom bars eat up too much real estate in that mode.
Click to expand...
Click to collapse
I'm thinking though that because of the way the phone was developed. If they wanted to, UI designed would quite easily put at least the top bar on one side. The bottom bar would be more tricky though. I suspect you'd do away with it and opt for a different navigation/menu paradigm. Or at least make fuller use by offering more menu options when there's more space available.
and as stated no real benefit apart from video
and games being as most devices buttons are laid out
Click to expand...
Click to collapse
This is what I'm not so sure about. These two are true, of course, but I suspect that the more we start inputting text on our devices, the more we'll use a landscape-style keyboard. When you start doing that in the calendars, SMS apps and other everyday tasks, having a phone in landscape suddenly becomes more appealing. 90% of the time I'm starting up my Tytn, it's to do something that requires some kind of text input. When this is the case, I'm wasting time starting in portrait then moving to landscape.
This is why I prefer CLAMSHELL devices or anything with a slide out tilting keyboard that would allow the screen to orient itself to landscape view. Unfortunately, there are no good clamshell out there except for an outdated HTC Universal.
anyone else experiencing slow tracking and movment when using google maps or latitude?
my GF's Wildfire S is perfect while my Galaxy S plus is slow to get GPS if it gets it at all and incredibly slow while using maps or latitude, its like when you used to play a game on a pc and the HDD would start thrashing lagging your game like crazy.
its as if something is trying to access cpu in the background, im getting sick of this phone it was supposed to be a bit of an upgrade to my Wildfire S but all i see is the Wildfire S kick its arse even with that 600Mhz cpu compared to my 1.4Ghz cpu.
can you check please how it runs by clicking the compass icon top right while looking at the map and setting it to follow you so the map moves around you when you turn.
Thanks
Hi BackDaws,
This is a common problem it seems across the SGS+ phones as I have also been facing the same problem. This is what I have found and you may check it at your end aswell.
1. Enter the start and the end direction and the route comes up.
2. Now tap the Blue icon which states your current position and it will now come to the centre of your screen.
3. Then press the cmpass icon on the top right. Now your screen will refresh as you move but now the problem that you will face is that the whole route has been compressed in one screen and you will not be able to make out if there are frequent turn in your rout.
4. Now go the Zoom out tab that is there at the right bottom corner and Zoom it to a level where you can see the route clearly with the turns.
See if this helps... It has helped me but there are times when the refresh rate is slow because of the data transfer rate.
Also do let me know if you find any other way out
Thanks
Sunil
Hi all,
I notice that when sliding through the app drawer of TW3, the finger tends to move some distance before the page starts following the finger. This is especially obvious when then page is stationary and the finger has to move some distance before the app drawer page stutters and starts moving.
After reading most if not all of the discussions in this forum, I understand that our phone sustain certain level of lag in that situation, probably due to the touch mechanism itself or inefficiency in the processor or what not. But I do have an interesting observation: whenever my phone sustains a fresh reboot, it is that time that the app drawer is perfectly lagless and follows even the tiniest movement of my fingers. This snappy phenomena only lasts until I put the phone to standby, i.e. locking the phone. Thereafter it goes back to the condition as mentioned earlier on.
My question is, there's no doubt i9003 has the capability to be lag free in the context of this discussion, but it seems pretty apparent that something is inhibiting the phone from being as smooth as when it first rebooted. Could it be the priority the TW launcher is assigned with, or does the processor clock speed matter in this situation?
P.S. When testing, I made sure that no applications are opened after the fresh reboot, so issues like insufficient memory etc should not be related here.
I noticed the same things, not only when sliding through the app drawer, but also when sliding menus etc. However after a reboot, my phone behaves as always. Maybe you feel it more lagfree because of the high clock speed due to the multiples stuff your phone does on boot. Try to change your governor to performance and see if it behaves like after a fresh reboot. In this way you'll know if your lagfree experience is due to clock speed.
I read a lot of stuff too but nothing was really useful. However I noticed that I feel lags only when the touch of the screen can be interpretated in different ways (for example sliding screens and opening apps), but when touching the screen allows you to do only one thing, like moving things, there are nearly zero lags. For example when you pull down/up your notification bar or when you move a zooomed image in gallery. This make me think that it's more a software problem than a hardware problem and I think that because in some app there are less lags than in others.
I don't know if you read this, but I think it improves the touchscreen, even if the difference is barely noticeable.
TW3 is sludge!
Is there any speed-governor app for the Xoom that can be configured to lock the CPU to 1000MHz whenever the soft input area is active (or better yet, whenever Graffiti input is active), and/or a way to increase the digitizer sample rate?
Historically, Graffiti has been totally unusable on my Xoom. Literally, so low of a sample rate, and so many errors, that I just couldn't use it. I finally got around to unlocking and reflashing my Xoom to CM10 last night, and locking the CPU to 1000MHz makes it work a lot better... but the accuracy is still a cruel joke compared to even my creaky, old Hero overclocked to 711MHz.
It's pretty sad, actually. On the Hero, the digitizer seems to be reporting samples at least 4-16 times as often, and I can get nearly 100% accuracy without even trying. On the Xoom locked to max speed, it seems to do a tiny bit better than my S3 gets with stock, but the sample rate still appears to be absurdly low compared to what it was on the Hero, and feedback seems to lag the actual touch by at least 100-200ms. On the Hero, feedback was literally instant... stroke, and see the pixels turn white INSTANTLY under my fingertip. On the Xoom (locked to max), they start turning white a fraction of a second after I touch the screen, and I can see the last bit of the stroke render a fraction of a second after I lift my finger away. With the stock Xoom rom, it was more like, "draw the character, and see a jagged impression of it sputter into existence about a half-second later... maybe, MAYBE even getting recognized correctly about 70% of the time".
I'm guessing that either the Xoom's digitizer has a limited sample rate, or something in the kernel or driver is limiting the sample rate... but I'm still trying to find a straight answer somewhere about whether/how you can build a custom kernel without losing your ability to run paid Market apps. Or whether it's even necessary to go to that extreme, as opposed to something like a setting that tells Android to increase the sample rate, or not throttle the CPU when an input area is active, or maybe a way to let something like SetCPU identify "soft input area active" as a profile-triggering condition. I'm also pretty sure that the Xoom's kernel (if not recent versions of Android itself) try to treat the existence of a soft input area as an excuse to massively throttle the CPU, on the theory that it's just displaying a picture of a keyboard and waiting for a blunt press. HOWEVER, I'm SURE there HAS to be an equally-official way of defeating that behavior, if only because it would also screw up Android's ability to handle east Asian input methods.