Related
Got my touch pro yesterday after dropping my Hermes and killing the GSM radio.
After using it for 24 hours I can make the following obsevations.
Of course it comes in a designer box (upside down pyramid)
included accessorys (of the top of my head)
-battery
-headphones with mic (no answer/hang up button)
-Wall charger with usb "A" host port on it
-Usb A to a micro lead for charger and activesync
A big hit for me is the new holder, sure it doesnt clip on my belt, but you can still use the device whilst its in the holder, you just need to slide it out a bit.
I miss the Jog wheel from the Hermes, and it takes a while to get used to TF3D scrolling.
When you first open the device, it appears to lack a D pad, its there however just a bit tricky to use (press around the outside of the circle)
Pros
New CPU seems to make a big difference
TF3D scrolling and nav is tricky to get used to but works well.
Text in menus etc is large to compensate for the fact you use your thumb and not a stylus 99% of the time
5 row keyboard is more logical and doesnt assign a million things to one key
usable shortcuts on the keyboard
landscape on the home screen has handy shortcuts
tf3d homescrren is very usable (just wished it marked texts as read faster)
smaller than the hermes
nhuge amounts of storage and program memory
flat screen makes life much easier when using thumb/finger on the screen, (no more hitting the clock instead of X)
A2DP actually works whilst on a data network (you needed to disable the radio on the hermes to get gapless playback whilst walking)
Cons
Lower battery life than the hermes (you didnt expect this?)
No jog/scrollwheel (TF3D does NOT work in menus)
S2U2 crashes in configuration mode (havent investigated)
G sensor is terrible in opera, rotates page back to portiat when in landscape CONSTANTLY (open keyboard to force landscape)
keyboard buttons are smaller takes some getting used to (the amount of times i have hit capslock instead of A)
no turn by turn nav software by default (tytn ii had copilot)
Other than that im loving it.
The turn by turn software is normally supplied by the provider, for example T-mobile tend to give away co-pilot,
having said that HTC have supplied some of their devices with tomtom as of recent.
Apologies if this has been thoroughly covered, I went back 4-5 pages in each forum but didn't see anything.
From what I can gather from reviews and youtube videos the D-pad on the Touch pro works like a standard D-pad, and when in opera can be used to zoom in by circling it with a finger like a click wheel on an Ipod. Is it possible to modify it to work as a scroll wheel instead of a "zoom wheel". I know this isn't an option out of the box, but is it something that's possible, or being worked on?
I'm considering from the tilt, and while I've convinced myself that I don't need the hard left and right buttons, or the email & browser buttons, I'm not sure I'll be able to get used to working without any kind of jog dial/scroll wheel.
I think it's been asked and the answer is not yet.
The D-pad is one of the things I really don't like about the phone though, the buttons are all on the same plane, not separated in any way, and that makes it very difficult to differentiate the d-pad from the home/back/send/end buttons. I didn't find it was a problem until playing games, when I kept minimizing the window by hitting the Back button.
oh... the touch pro has a d-pad??? omg ive had the phone for almost a month and i only just discovered it. i thought it was just a scroll thing. its really hard to press though..
Black93300ZX said:
I think it's been asked and the answer is not yet.
The D-pad is one of the things I really don't like about the phone though, the buttons are all on the same plane, not separated in any way, and that makes it very difficult to differentiate the d-pad from the home/back/send/end buttons. I didn't find it was a problem until playing games, when I kept minimizing the window by hitting the Back button.
Click to expand...
Click to collapse
Well I don't really play a whole lot of games on my phone, but I do read a lot of really long email threads, and more importantly, when I'm bored I read sites like overheardinnewyork.com which is basically a lot of text to scroll through.
I'm getting the feeling that I'm going to have to find a way to "play" with a TP and see if I love it or not. I went 8125, x01ht, tilt, and now I'm looking to upgrade. but if this phone isn't going to rock me, I'll hold out (for what I don't know).
As much as I like flashing new roms to my tilt, it seems all anyone does is try to rip the best features from other phones...so at some point I might as well just get the other phone.
Diamond Tweak 0.5.3 allows you to enable d-pad scrolling for some applications.
http://forum.xda-developers.com/showthread.php?t=409540
(you need to soft-reset after you have changed options)
dougalls said:
Diamond Tweak 0.5.3 allows you to enable d-pad scrolling for some applications.
http://forum.xda-developers.com/showthread.php?t=409540
(you need to soft-reset after you have changed options)
Click to expand...
Click to collapse
Hmmm, looks promising. Have you tried it? I just can't imagine I'd ever use the zoom feature, although up to now I've used opera mini, so perhaps after switching to opera mobile I'd change my mind. But I'm still pretty sure I'd prefer to double tap the screen to zoom, and have another means of scrolling.
I have tried it and it works well for contacts (useful), programs etc but does not work with my Yahoo inbox (possibly due to the ROM I am using - ROmeOS v1.22) and it does not replace the zoom in opera. You can set up custom applications in DiamondTweak so it may be possible to overcome any differences between ROM's by setting up a custom application. I do use the zoom in opera so wouldn't want to replace it.
You can still double tap to zoom in/out on opera, as well as the wheel - the wheel lets you zoom in/out in small increments, double tapping toggles between full page and zoomed in.
DesCo said:
Hmmm, looks promising. Have you tried it? I just can't imagine I'd ever use the zoom feature, although up to now I've used opera mini, so perhaps after switching to opera mobile I'd change my mind. But I'm still pretty sure I'd prefer to double tap the screen to zoom, and have another means of scrolling.
Click to expand...
Click to collapse
Think about this, with Opera Mobile you'll only have 2 levels of zoom ("in" or "out") unless you use the wheel to zoom. I liked being able to use it to fine tune and get things to look just right, but that's me. Try it out and see what you think.
With newer versions of Opera Mobile, there is now an on-screen zoom slider that adds a "tap and slide" button for incremental zooming. Now I find myself wanting an alternative to scrolling, since my finger otherwise covers up part of the screen and might accidentally click a link. Unfortunately the arrows and dpad don't scroll the page but instead jump from link to link.
This has been one detail (although a minor detail) that has made be begin to consider replacing my TP with the X1, since the X1's optical sensor dpad apparently provides scrolling functionality.
DesCo said:
Hmmm, looks promising. Have you tried it? I just can't imagine I'd ever use the zoom feature, although up to now I've used opera mini, so perhaps after switching to opera mobile I'd change my mind. But I'm still pretty sure I'd prefer to double tap the screen to zoom, and have another means of scrolling.
Click to expand...
Click to collapse
use advance config 3.3 ........search for the link
go to options, click smart touch and it allows you to add any application, where in touch wheel (above D Pad) can be used for scrolling......i use it for contacts, file manager, program, call history, phone window, mails, messages and its really usefull and very cool........i dont use it for opera and internet explorer and use it for zooming as put in default
~
Kingjack
Thanks for the info. As I said, I haven't picked up the TP yet, I'm holding out for the Fuze (or a reasonably priced GSM model).
To change gears a bit, I'm curious, what kind of difference do people see in using cooked Roms on this device. I only ask because as a Kaiser user I'm used to using Roms because they incorporate features from the latest equipment. But as this is among the newest models out, and a "flagship" phone so to speak...is there much of an advantage over say a stock ATT rom minus the bloat? I enjoy high level of customization, and being able to pick my features, but as this is a relatively new device, I don't want to go through the trouble of unlocking and flashing if there isn't going to be a real gain in performance/features, or if it's going to impact performance (like trying to run Manilla 2d on a Kaiser, and pretending that a 5 second screen rotate time is ok)
PS: just for the record, despite my incredibly low post count, I've been lurking on the board for ~2 years...I'm not some (I hate this word) newb asking "what rom is best" or "can someone explain to me how to XXX reading the Wiki is too much work"...just wanted to throw that out there.
Volume buttons for scroll
Review on wmexperts of Sprint Touch Pro has the information below in the comments area. Looks like the reviewer followed up with the statement that he used AE Buttons to remap the volume buttons on the side, where the scroll wheel is on 8525/Tilt to scroll up and down with each click. I don't have Fuze, but it seems like this would work on it as well, I don't think it's a free softare though.
http://www.wmexperts.com/reviews/smartphones/review_24_hours_with_the_sprin.html
Buttons: I have successfully used AE Buttons to successfully remap the volume up and down buttons. I have the volume down button set at one click to scroll down and a log click for OK/Enter. The volume up button is set at one to scroll up and the log click Alt/Tab Wisbar's switch utility. I have also remapped the Back button to OK/Enter. The Home button now brings down the Start Menu on a single click and Email when I hold it down. This has made life a lot easier and has in virtually increased my available hardware buttons to a more comfortable level of usable buttons.
cparkhorn said:
Review on wmexperts of Sprint Touch Pro has the information below in the comments area. Looks like the reviewer followed up with the statement that he used AE Buttons to remap the volume buttons on the side, where the scroll wheel is on 8525/Tilt to scroll up and down with each click. I don't have Fuze, but it seems like this would work on it as well, I don't think it's a free softare though.
http://www.wmexperts.com/reviews/smartphones/review_24_hours_with_the_sprin.html
Buttons: I have successfully used AE Buttons to successfully remap the volume up and down buttons. I have the volume down button set at one click to scroll down and a log click for OK/Enter. The volume up button is set at one to scroll up and the log click Alt/Tab Wisbar's switch utility. I have also remapped the Back button to OK/Enter. The Home button now brings down the Start Menu on a single click and Email when I hold it down. This has made life a lot easier and has in virtually increased my available hardware buttons to a more comfortable level of usable buttons.
Click to expand...
Click to collapse
How have you managed to get AEButton working on your home button?
I found that the home and back buttons seem to be "hard coded" to do their tasks, and AEbutton only assigns an *additional* task to each button. In other words, when I press Home for start menu, it first goes home, and then opens start. If I map the back button to Camera, it first goes back an application screen, then launches camera. Very annoying. The only buttons I found AEButton works with is the vol up and down. Is there a trick I'm missing?
Just got a Lumia 800 and I feel that when I scroll sometimes it interpretes my "scroll swipe request" as a tap and enters e.g an application. This is clearly visible when surfing using the browser when I keep zooming in and out when I try scrolling too fast (by lifting and dragging the finger in a fast motion).
Any clue why this is happening or is it just me being too comfy how Android handles things?
Aloha all, Having trouble knowing how to ask this...bear with me.
I am having problems with the menus that are triggered by the 'hover' action of a mouse. Using the surface pro or even my lumia 920 I am frequently unable to operate many menus on sites.
officefootballpools.com tournamentpools.com and a host of other sites have the same type menus.
Normal action would be with a mouse and when you hover it drops down a menu that you click your selection. Its isn't a normal drop down but a .li. html type for the menu.
Im sure this has been discussed but I was looking for some vocabulary so I can search the right threads.
You cant interact with hover images via capacitative touch. The browser has no way to tell if you want to click or just show the drop down, it assumes click. Some sites (with limited success) I have managed to press and hold on a link to show its drop down, then if you ignore the usual right click popup then you can sometimes hit the correct icon, this is on a lumia 710.
Otherwise if you have a device with an active stylus (the surface pro for example) you can get rollover easily. If you notice when you hold the pen a tiny bit off of the screen you get a little dot appearing on the screen where the pen is pointing without any physical contact. This dot can trigger rollover events as in this case windows knows that you are not touching the screen, touch becomes a click, hovering the pen over the screen becomes mouse movement which is enough to trigger rollover.
Thank you for your reply. I understand and assumed the same. I have been working with an x61t for a few years so the jump to capacitive has thrown me a bit.
Okay, so what are web developers doing instead of this type of drop down? I recently read an article that says a lot of developers are moving to the new msn.com type format with nav bars on left or right with no hover...
Anyway thanks again. The volume of sites with this issue is pretty large. Yahoo.com/fantasy chokes a donkey, etc.
Side question, does Win8 have the on screen mouse that I used to have on my Lenovo? Or is that a Lenovo product probably?
Alot of web developers are doing nothing at all. In some cases clicking the link that causes the dropdown redirects to a page listing the other links in that dropdown, that's always handy. Usually most devs create mobile versions of sites which are normally touch friendly. I have seen 1 or 2 sites create iPhone versions before, these worked nicely on android so I would assume they are fine on the lumia and maybe the surface.
I haven't ever seen an on screen mouse before but if there is not one in windows 8 then there may be a 3rd party one somewhere. I am on my phone right now, otherwise I would have looked myself.
One advantage of using "Mobile" websites is that they should be designed with the limitation of touchscreens - specifically, the inability to track hover - in mind. That may help you out.
Alternatively, the Surface Pro uses an active Wacom digitizer (as well as a touchscreen) that can sense the pen at a distance. You can use the stylus pretty much perfectly as a mouse, with hover and right-click and everything.
So MX Player finally has playback speed adjustment (yay!) but unfortunately the method of accessing it cumbersome (if you don't want to use gestures). Fortunately that's just a UI issue (which I suspect is considerably easier to fix than implementing the speed control in the first place).
The problems that I see are a follows:
1. You have to dig down several menus deep to reach it.
2. The speed control overlay remains permanently on screen and does not hide with the rest of the onscreen controls. If you close it because you want to see the full screen without the clutter, then every time you want to make a speed adjustment you have to drill back down through the menu, make the adjustment, and then close the window again.
3. Once the playback speed adjustment overlay window has been closed, there is no longer any visual feedback as to the current playback speed.
4. Because the playback speed control is a separate overlay window (rather than being attached to the rest of the onscreen controls) it jumps around all over the place when the other controls appear and disappear (causing mis-clicks if, for example, you are trying to repeatedly tap the + or - buttons to adjust speed).
What I would like to propose is a single speed control icon button (with digits showing the current playback speed) that displays as part of the regular onscreen controls. For example, it could be placed next to the HW+ button on the top control bar (although if I had my own way, I would move the lock button up next to the HW+, then move the 'fit to screen' to where the lock button was (to the left of the rewind / go back button), and then put the new playback speed button in it's place (to the right of the fast forward button). But that's just me.
Anyway, regardless of positioning, it would be incredibly useful to always be able to see the current playback speed with just with a single tap (because it would display as part of regular oncreen controls) as well as being able to easily adjust speed with from the main screen without having to drill through menus.
A slider control would allow quick adjustment of large speed changes instead of having to go tap, tap, tap, tap, tap, and it would make speed adjustments more fluid from a usage point of view. The slider could still be 'notched' to adjust in steps if the user drags slowly (so that reaching an exact playback speed value can be achieved if required).
Another idea that I've just had is perhaps there could be an option to display the speed control slider by long-pressing the play button. That seems as intuitive a place to control playback speed as anywhere else. The current playback speed could be displayed as digits either above or below the play button itself (so you'd always know the current speed).
Just some suggestions for your consideration.
Cheers.
I think you not aware of the gestures.
Just swipe up/down with two fingers to change the playback speed. I think, there can't be a fastest way than this one.
Drewett said:
So MX Player finally has playback speed adjustment (yay!) but unfortunately the method of accessing it cumbersome (if you don't want to use gestures). Fortunately that's just a UI issue (which I suspect is considerably easier to fix than implementing the speed control in the first place).
The problems that I see are a follows:
1. You have to dig down several menus deep to reach it.
2. The speed control overlay remains permanently on screen and does not hide with the rest of the onscreen controls. If you close it because you want to see the full screen without the clutter, then every time you want to make a speed adjustment you have to drill back down through the menu, make the adjustment, and then close the window again.
3. Once the playback speed adjustment overlay window has been closed, there is no longer any visual feedback as to the current playback speed.
4. Because the playback speed control is a separate overlay window (rather than being attached to the rest of the onscreen controls) it jumps around all over the place when the other controls appear and disappear (causing mis-clicks if, for example, you are trying to repeatedly tap the + or - buttons to adjust speed).
What I would like to propose is a single speed control icon button (with digits showing the current playback speed) that displays as part of the regular onscreen controls. For example, it could be placed next to the HW+ button on the top control bar (although if I had my own way, I would move the lock button up next to the HW+, then move the 'fit to screen' to where the lock button was (to the left of the rewind / go back button), and then put the new playback speed button in it's place (to the right of the fast forward button). But that's just me.
Anyway, regardless of positioning, it would be incredibly useful to always be able to see the current playback speed with just with a single tap (because it would display as part of regular oncreen controls) as well as being able to easily adjust speed with from the main screen without having to drill through menus.
A slider control would allow quick adjustment of large speed changes instead of having to go tap, tap, tap, tap, tap, and it would make speed adjustments more fluid from a usage point of view. The slider could still be 'notched' to adjust in steps if the user drags slowly (so that reaching an exact playback speed value can be achieved if required).
Another idea that I've just had is perhaps there could be an option to display the speed control slider by long-pressing the play button. That seems as intuitive a place to control playback speed as anywhere else. The current playback speed could be displayed as digits either above or below the play button itself (so you'd always know the current speed).
Just some suggestions for your consideration.
Cheers.
Click to expand...
Click to collapse
Thirumalai.K said:
I think you not aware of the gestures..
Click to expand...
Click to collapse
I am perfectly aware of gestures, which is why I mentioned it in the very first sentence of my post above.
Drewett said:
So MX Player finally has playback speed adjustment (yay!) but unfortunately the method of accessing it cumbersome (if you don't want to use gestures) ...
Click to expand...
Click to collapse
My point is that: (a) gestures are not a replacement for good UI design (they are an additional means of accessing a feature), and (b) I don't want to use gestures for playback speed because I use gestures for zoom and pan (and it's a nightmare trying to pan without constantly messing up playback speed by accident).
I already get enough grief from messing with the volume whenever I try to swipe down to check my phone notifications (I would much prefer a volume slider). I don't need the same with playback speed too.
The existence of a gesture control does not mean that the menu method of access can't also be improved for a better user experience for users who do not want to use gestures.
I would love a playback speed option easily accessible once I touch the screen, rather than the 2 fingers gesture or going into audio options, it would be so great to have it appear on 1 click and then we adjust the speed.
From 1.9.1 you can now use Ctrl + UP/Down keys on the physical keyboard to increase and reduce the speed.
Regarding more easily accessible UI option, We have some plans for UI improvements in future (after implementing some other important features). It will be implemented as a part of UI overhauling.
Thirumalai.K said:
From 1.9.1 you can now use Ctrl + UP/Down keys on the physical keyboard to increase and reduce the speed.
Regarding more easily accessible UI option, We have some plans for UI improvements in future (after implementing some other important features). It will be implemented as a part of UI overhauling.
Click to expand...
Click to collapse
great
Thirumalai.K said:
From 1.9.1 you can now use Ctrl + UP/Down keys on the physical keyboard to increase and reduce the speed.
Regarding more easily accessible UI option, We have some plans for UI improvements in future (after implementing some other important features). It will be implemented as a part of UI overhauling.
Click to expand...
Click to collapse
It would be great if there would have been an option to select the physical buttons to control the playback speed. This is suitable for android TV controls. By default up/down buttons on android TV remotes for example are used to control volume, which is useless on TV. These buttons would be perfect to control playback speed instead.
jackice said:
It would be great if there would have been an option to select the physical buttons to control the playback speed. This is suitable for android TV controls. By default up/down buttons on android TV remotes for example are used to control volume, which is useless on TV. These buttons would be perfect to control playback speed instead.
Click to expand...
Click to collapse
have you tried Ctrl + UP/Down?
Thirumalai.K said:
have you tried Ctrl + UP/Down?
Click to expand...
Click to collapse
I don't have ctrl button on my android TV remote
jackice said:
I don't have ctrl button on my android TV remote
Click to expand...
Click to collapse
Each remote has different buttons & they provide different key input. We use the standard key events defined on android itself.
Probably your remote have separate keys for volume button. But, in many devices (especially android boxes) only DPAD is exists.
So, configuring UP/Down to control the speed will cause issues with them. And many people uses external keyboards as well. It will break that too.
Anyhow, we will discuss the other possibilities with our team and we will improve the same if it's possible.