Anyone know if it is possible to change the TyTn's annoying habit of making unwanted reversions from landscape to portrait orientation?
On my machine it:
1. Always changes to portrait when the device is switched on, even if it was in landscape when it switched off. Some idiot obviously thought this was a "feature" since it comes up in landscape initially and then switches to portrait as you watch.
2. Changes to portrait when the keyboard slide is closed even if it was in landscape before the slide was opened. This is a useful feature poorly thought through. Auto switch to landscape on open IS logical, but it should not assume you want to go back to portrait when the slide is closed again.
I'd be very happy if I could just disable both these "features", but ideally I'd be able to keep "switch to landscape on slide open", with or without "revert to previous orientation on slide close".
JohnHind said:
Anyone know if it is possible to change the TyTn's annoying habit of making unwanted reversions from landscape to portrait orientation?
On my machine it:
1. Always changes to portrait when the device is switched on, even if it was in landscape when it switched off. Some idiot obviously thought this was a "feature" since it comes up in landscape initially and then switches to portrait as you watch.
2. Changes to portrait when the keyboard slide is closed even if it was in landscape before the slide was opened. This is a useful feature poorly thought through. Auto switch to landscape on open IS logical, but it should not assume you want to go back to portrait when the slide is closed again.
I'd be very happy if I could just disable both these "features", but ideally I'd be able to keep "switch to landscape on slide open", with or without "revert to previous orientation on slide close".
Click to expand...
Click to collapse
I don't have problem #1, and I wonder if it's being caused by the orientation sensor being triggered at the wrong time. The sensor is magnetic, so if there is a magnet (any magnet) making contact the screen orientation will be landcape. Others here have noticed that even the magnetic closures on the official Tytn case from HTC will trigger the change.
Problem #2 is strictly software and yes, it's damn annoying when a UI designer assumes that the only functionality needed is the one that best fits his/her needs with no regard to anyone else. The only solution I can offer you, short of writing an app to do this yourself is to map a key to orientation switching and switch it yourself once you retract the keyboard. (A side gripe here is why the orientation settings are buried so deep that only a power user can find it).
I think I did see an app for changing orientation but will need to search.
By the way it starts (sometimes) in landscape because the mechanism that changes orientation is a magnet switch. A magnet on the keyboard is moved when you slide it open and operates the switch. Howver since there are powerful magnets in some carrying cases these can operate the switch (as if the keyboard was open) Then when you take it out of the pouch it takes a second or to and reverts to portrait.
You can operate the switch manually by running a magnet along the side of the casing. (not that I'm suggesting that as a solution )
EDIT: perhaps this will help
http://forum.xda-developers.com/showthread.php?p=1098622#post1098622
Mike
Thanks guys.
I have been able to get a rotation icon on the today screen (iLauncher) and to map rotation to a hard-key using a combination of iLauncher and Resco KeyMapper. But rotation takes a noticable time (seems to redraw at least four times, probably a poor model for the today screen plugin architecture) and it is irritating to have to do it twice when you do not want it at all.
With further experimentation I find it goes according to the slide position when switched on - if you open the slide and then turn on, it always switches to landscape, if you switch on with the slide closed it always switches to portrait. I suppose this makes sense - it reads this magnetic switch at power on and acts accordingly. But if Rob is right, maybe this is a "feature" of one of the utilities I've installed. Next time I have to do a hard reset I'll see if it still happens with the base OS.
I was really hoping there'd be a registry key I could change to modify this behaviour or that there'd be some utility I could buy that allowed me to hook any action I wanted to the slide switch (or none). For example, it would be more ergonomic if it turned on on opening the slide as well as changing to landscape.
See what you mean about the magnet - maybe if I got a strong enough one it would permanently magnetise and stick!
Having written StylusLock I wanted an additional lock/unlock method. Although StylusLock works great, I wanted some extra features:
* to have it possible to lock and unlock "one handed". The StylusLock approach cannot be done "one handed", e.g. on a bike.
* Also some people do not like to operate with the StylusLock (always).
* The combination with this new CapacitiveFingerLock and existing StylusLock will suit more people.
* And sometimes people will use the Stylus, so they will get the right behaviour depended on the usage pattern
* Still the goal is to let it consume almost no CPU and battery and KISS to operate
I discovered with StylusLock that when the TouchPanel and Hardware keys are locked, still the Zoom function works in e.g. Opera.
You can try yourself, using StylusLock:
1. Start Opera
2. Lock the Touch Diamond or Touch Pro with StylusLock
3. TouchPanel and all hardware keys are locked
4. Try to Zoom in/Zoom out in Opera, this still works with the NavWheel
5. Also the Ok button seems to react
I figured out via Scott Seligman and Koushik Dutta how to programmatically access the Capacative Touchpads. You can read also more here: [REF]Capacitive touchpad apps
So this idea is implemented in CapacativeFingerLock. But I am not using the NavWheel idea, but just uses the Capacative hardware area for locking/unlocking. The idea is again simple and clever. When you softly touch the area where the hardware keys are located (so do not press the keys, just gently touch them), the up/down and position area can be detected. I programmed that when the same area is touched gently 3 times within a second (without touching another area), the lock status is toggled.
I made a proof of concept program (just copy the exe inside the zip file attachment to your phone and just execute it), which shows how it is going to work. Just play around with softly touching the hardware panel, to see what happens.
If am working on integrating CapacativeFingerLock with StylusLock, to have a working "real locking" application. The Proof of Concept program just shows that it is possible.
Reserved for future use
Another one for future use.
very nice concept....now i noticed you posted a link of this thread in the wheel to unlock thread...would there be a way to possibly implement a config tool that lets you choose say, touch 3 times softly, or run your finger around the circle?
Malik05 said:
very nice concept....now i noticed you posted a link of this thread in the wheel to unlock thread...would there be a way to possibly implement a config tool that lets you choose say, touch 3 times softly, or run your finger around the circle?
Click to expand...
Click to collapse
In principle this can be done. But because the NavWheel is also used for other purposes (Zoom In/Out), I have chosen not to use the NavWheel, but the 3 times gently touching. In this way there is no interference with other existing applications.
I'll try that, it seems like no one cares aboyt the capacitive touch pad, it seems like an amazing thing that we've got that is so neglected. I hope to give some positive feedback later, but first I have some rom flashing to play with!
Thanks for the work, there must be so many possible implementations for this, I hope this is just the beginning of something much bigger.
How about a simple tap to launch app?
i went ahead and installed it, and it works very well...Will there be a (pretty) GUI to show that it was unlocked?
Also the diamond does have multi touch on that pad area, which enables a "trace" of the movement of your touch
http://www.youtube.com/watch?v=f3Owgcos_KY
Since the nav sensor wont be so ideal, how about sliding your finger from the top of the pad to the bottom (lets say, place your finger on the back button, and gently moving it down to initiate unlock, with a GUI on the screen following your movement, as you go closer to the bottom, the color changes from lets say, red, to green...with incremental color changes in between)
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
surur said:
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
Click to expand...
Click to collapse
I imagine it is just harder to implement for a proof of concept.
Personally I think there are enough ways to lock the diamond, whether you swipe the screen or 1cm below it is not a revolution, but if swiping the capacitive touch pad could be made to launch desired apps from selected gestures, that would be a revolution, like dynamo3 or hibernate or even standby. I think a lot of people here would want that over another locking solution. Good will intended!
Just tried it.
This is very cool very very cool
Thanks for time invested in such a cool development.
surur said:
Instead of 3 taps, why not a swipe between the home and back keys, which seems much more natural.
Surur
Click to expand...
Click to collapse
Swiping is not so easy one handed. Touching gently 3 times is much easier one handed, holding your Touch Diamond or Touch Pro firmly and touching with your thumb.
However, I can imagine other sort of applications which can use the swiping for other sort of operations. Both are possible with the programming API I made.
uniqueboy said:
I imagine it is just harder to implement for a proof of concept.
Personally I think there are enough ways to lock the diamond, whether you swipe the screen or 1cm below it is not a revolution, but if swiping the capacitive touch pad could be made to launch desired apps from selected gestures, that would be a revolution, like dynamo3 or hibernate or even standby. I think a lot of people here would want that over another locking solution. Good will intended!
Click to expand...
Click to collapse
I am going to share the source code. I have written it in C#. And others can get ideas and take over some of the source code for their own application. At the end we profit all of it.
ZuinigeRijder said:
I am going to share the source code. I have written it in C#. And others can get ideas and take over some of the source code for their own application. At the end we profit all of it.
Click to expand...
Click to collapse
I like your style, that is the the kind of development attitude that keeps here!
ZuinigeRijder said:
Swiping is not so easy one handed. Touching gently 3 times is much easier one handed, holding your Touch Diamond or Touch Pro firmly and touching with your thumb.
However, I can imagine other sort of applications which can use the swiping for other sort of operations. Both are possible with the programming API I made.
Click to expand...
Click to collapse
If you are open to other ideas, I would love the area from the back to home key to be a scroll bar when the device is in landscape mode. Grabbing the narrow on-screen scroll bar can be tricky, and the Touch Pro lacks the scroll wheel of the HTC Kaiser.
Surur
Have been looking into this myself as well. The only code I found was managed C#. Do you think we can use this in our native C code? Looks promising though!
ZuinigeRijder said:
Having written StylusLock I wanted an additional lock/unlock method. Although StylusLock works great, I wanted some extra features:
* to have it possible to lock and unlock "one handed". The StylusLock approach cannot be done "one handed", e.g. on a bike.
* Also some people do not like to operate with the StylusLock (always).
* The combination with this new CapacitiveFingerLock and existing StylusLock will suit more people.
* And sometimes people will use the Stylus, so they will get the right behaviour depended on the usage pattern
* Still the goal is to let it consume almost no CPU and battery and KISS to operate
I discovered with StylusLock that when the TouchPanel and Hardware keys are locked, still the Zoom function works in e.g. Opera.
You can try yourself, using StylusLock:
1. Start Opera
2. Lock the Touch Diamond or Touch Pro with StylusLock
3. TouchPanel and all hardware keys are locked
4. Try to Zoom in/Zoom out in Opera, this still works with the NavWheel
5. Also the Ok button seems to react
I figured out via Scott Seligman and Koushik Dutta how to programmatically access the Capacative Touchpads. You can read also more here: [REF]Capacitive touchpad apps
So this idea is implemented in CapacativeFingerLock. But I am not using the NavWheel idea, but just uses the Capacative hardware area for locking/unlocking. The idea is again simple and clever. When you softly touch the area where the hardware keys are located (so do not press the keys, just gently touch them), the up/down and position area can be detected. I programmed that when the same area is touched gently 3 times within a second (without touching another area), the lock status is toggled.
I made a proof of concept program (just copy the exe inside the zip file attachment to your phone and just execute it), which shows how it is going to work. Just play around with softly touching the hardware panel, to see what happens.
If am working on integrating CapacativeFingerLock with StylusLock, to have a working "real locking" application. The Proof of Concept program just shows that it is possible.
Click to expand...
Click to collapse
A while ago I posted about the Windows Messages received by the form for capacitive touch events. Is that what you ended up using to figure out where on panel is being touched? Mind posting some code so I can add it to the Sensors assembly?
Great idea. Defienetly it will be my way of locking device. StylusLock works nice but can't be operated by one hand so its useless for me. SensorLock uses battery and i've drop my phone already unlocking it.
surur said:
If you are open to other ideas, I would love the area from the back to home key to be a scroll bar when the device is in landscape mode. Grabbing the narrow on-screen scroll bar can be tricky, and the Touch Pro lacks the scroll wheel of the HTC Kaiser.
Surur
Click to expand...
Click to collapse
This can be surely done, programmatically. But I do not know if you can control the scrolling of other applications. The latter seems to me difficult?
Anyway, when a lot of applications are going to use gestures using the capacative areas, there will be going conflicts (different programs reacting differently on different gestures).
For the locking application I want to made, I see also some different gestures possibilities:
- 3 taps for locking/unlocking
- swipe left to right for Power off
- swipe right to left for starting a configured application
And I am sure I can come up with other gestures and actions....
drvdijk said:
Have been looking into this myself as well. The only code I found was managed C#. Do you think we can use this in our native C code? Looks promising though!
Click to expand...
Click to collapse
Actually I started with C++ and had also a working Proof Of Concept. However, because I am new to Windows Mobile Programming, I also wanted to use C# as next project. I have developed programs in a lot of languages (also in C++ and C#), but I like C# more. And I wanted to do this now for Windows Mobile, to get experience with this. Note that the C# sample is using only .NET 2.0, so you do not need .NET 3.5.
You can find a C++ sensortest program, which was available on Scott's weblog:
http://scottandmichelle.net/scott/cestuff/sensortest.zip
ZuinigeRijder said:
This can be surely done, programmatically. But I do not know if you can control the scrolling of other applications. The latter seems to me difficult?
Click to expand...
Click to collapse
I dont know if you can manipulate the scroll bar of another application directly (though this would be ideal) but at the least maybe a page down keystroke could be sent to the active window.
Surur
Okay, I've done my best to search for posts like this before, and I'm not sure if this is an issue only for the Touch HD.
There are 100s of posts on how to plain disable screen rotation in opera, some of which work, some of which don't, regestry hacks, cabs, gsensor apps etc.
What I'm after is a simply fix to stop opera rotating all the way round (i.e. when you hold the bottom of the phone upright, it rotates back so the top of the screen is at the top).
Why may you ask? Because if you are lying down on your side (i.e. in bed) and you want to use opera, it's impossible, because the acclerometer is calibrated to the axis of the world, not your eyes.
Proposed solution: (if i'm not being a tool here and missing a previous post)
Prevent screen rotation of 180 degrees (i.e. include landscape in both directions, normal portrait, but not upside down)
IPhone does it, should be fairly simple, means you can hold it upside down and use a landscape mode comfortably.
Now i've had a crack at this myself, and there is nothing I can change in the registry, or in opera:config. Anyone got any ideas?
So far many apps are pretty lax in whether you hold the fire landscape with usb port on right or left. I was holding it to the left since I had it and had no problems.
Now I have a case like a book flap and I prefer the flap ontop hanging back,.usb port on the left. Couple.of.apps force it upside down, having to hold it the other way looks and feels stupid now. Anyone know if there's an app or what.exactly would control that? The kernel?
+1
//Tapatalk.KindleFire//
Found an app, Orientation Control
https://market.android.com/details?id=com.coinsoft.android.orientcontrol&hl=en
This has an override to force the landscape the other way. Only problem I've seen is if you have it set to autorotate like default, then those apps will still rotate counterclock. If you set this to forced, it will do it clockwise but lock and disable the auto rotate.
So an extra step if you know youll be using something for a while and worth manually setting and locking the setting.
my display is stuck in landscape now since yesterday while i was trying to install swiftkey x. i never actually got it installed so i cannot say it is the cause of having the display stuck. i was also tinkering around in nook colour tools, but cannot seem to find anything nook colour tools' settings that fixes my problem.
any feedback is appreciated.
Hey all, I like using the phone one handed and zoom buttons are essential. I also like being able to zoom with just a tap, as opposed to more convoluted methods (xScope/Naked Browser, I'm looking at you...). But the stock Android zoom buttons are ugly and less functional than the ones I had way back when on 2.2 (Bionix for the Samsung Vibrant).
Could anyone tell me where in could find the images for the Zoom buttons? I'd like to replace them with the ones from an older ROM, mentioned above. Think it would be somewhere in the SystemUI.apk?
If anyone is curious, the buttons I would prefer are transparent circles with a black outline. They're a good bit easier to press and you can see elements that would otherwise be obscured.
I'm the developer of Naked Browser. Naked Browser has the option to enable/disable the zoom buttons. It also has the option to enable/disable one-finger zoom. It also allows zoom with just a double-tap. Am I missing something?
aminaked said:
I'm the developer of Naked Browser. Naked Browser has the option to enable/disable the zoom buttons. It also has the option to enable/disable one-finger zoom. It also allows zoom with just a double-tap. Am I missing something?
Click to expand...
Click to collapse
Oh snap. No, it's just that one-finger drag zoom has poor performance (just isn't as smooth as it is on xScope). But I love your browser. It's why I mentioned it specifically. My niggle isn't to do specifically with Naked Browser or any other app, it's a system conflict. I think the stock zoom buttons are ugly and I want to swap them out with the zoom buttons I used on a different browser. It's easier to tap a round circle than it is to hit a little tic-tac. Also, the zoom buttons sometimes obscure elements in the bottom right and I have to wait until they fade out, so the transparent zoom circle buttons I mentioned in the first post would solve both of these issues. Rather than having you bloat up your fantastically minimal app, I'd prefer to do my own tinkering and fix the zoom buttons across my system.
I just wanted to say, your browser is fantastic. I found out about it just randomly perusing the big Android Themes and Apps forum and gave it a try. It's my default browser now. While I have your attention, if I could make a suggestion: you know how you have the swipe-from-edge toggle so the menu bars don't appear with unexpected frequency? It works great for making sure the bookmarks bar only opens with deliberate swipes. However, if you could provide a separate toggle for the address and tab bar, that'd be great. I never had a problem with the top bars appearing unintentionally. It's not much of a nuisance. However, in one-handed use, I have to reposition the phone in my hand and then swipe from the top to bring down that bar. On a big phone like the Nexus 4, you can understand how that extra little bit of effort adds up over a long browsing session.
Very cool. Thank you very much.
Let me address what you brought up:
One finger zoom in Naked Browser isn't as smooth as it is on xScope because:
- xScope is for newer devices. Naked Browser supports Froyo and newer and so far I've found that that kind of zooming isn't easy on older devices. That's really not much of an excuse because I could work on it. However, it could take days to figure out. I'm focusing on other features and bug fixes right now. Furthermore,
- I haven't used xScope in a long time but one finger zoom seems to work good enough in Naked Browser (no?). For comparison, it seems to work like crap in Google Maps, last I checked.
Regarding changing the zoom button pix, I use a smaller screen than you so I don't like the +/- buttons in a browser. I pinch zoom and I do it with one hand: small phone / big hands. Regardless, I'm adding your request to my list of items for the pro version.
Regarding adding the separate option for the menu gestures, I added those options (double swipe & swipe from edge) as afterthoughts. I feel that an experienced user of Naked Browser should turn both of these off because they've developed a feel for the menus, knowing instinctively how to avoid opening the bookmarks sidebar and top menu. For me it took about a week to get comfortable with it. Now, I think it is very efficient.
That being said, I may have messed up the gesture settings for larger screens as I don't have a tablet. What do you think about all this? Is it very hard to avoid opening the bookmarks menu? Tell me more about it, please.
Anyway, I hope you have luck changing the +/- on your devices and I do appreciate your feedback on Naked Browser. You're one of the few people I've seen mention stuff like this. Got my attention!
This is hijacking your thread for my app, so if you want to PM me or join me in the xda naked browser thread the feel free.
Thanks again, man. :good:
Hey, you've got a great app and I certainly don't mind helping it get more exposure. I know it's not a priority for you right now, but if it gets really popular, I'm sure you'll add a ton of lightweight features. That's how xScope became the best browser on Gingerbread!
On my Nexus 4, I've found that the bookmarks menu shows up by accident much more often than the URL/tab bar, and it's much more obtrusive when it does. It'd be nice to disable the bookmarks bar. I actually use the bookmarks menu a ton, so perhaps a better option would be to incorporate the menu button menu with the the bookmarks menu.
Also, I'm not sure if my options are causing it or its an inherent behavior, but it's inconvenient to have to scroll all the way to the top to bring up the URL/tab bar. I really wouldn't mind if it appeared every time I made any downward swipe. Maybe to accommodate other users, make the top half or quarter of the screen a zone that can pull up the URL/tab bar when the user swipes down from that region.
I basically want the navigation features of xScope but with the minimal, clean appearance of Naked Browser. I stopped using xScope because it's so bloated and unstable now. Naked Browser is 90% perfect for me. The 10% is just the menu behavior and tab navigation. xScope, for example, uses double tap and left/right to navigate between adjacent tabs while double tap and up/down to zoom. But if this decreases performance as it did on xScope, I'm happy with Naked Browser the way it is.
Maybe I need to optimize the swipe sensitivity for devices like the Nexus 4. I need to check one out, but for now the next update will reduce sensitivity somewhat. Regarding the separate gesture options, I had thought about adding them but I was resistant because I don't want to clutter the options view. However, I think it is the right thing to have and you've convinced me of how sorely it is needed. The next update will have them! I've tried it out and I like it.
If you press the device menu key it should show the top menu from anywhere on the page. Devices without a menu key should have 3 dots in a row that act as the menu key. Making it appear for every downward swipe is an interesting idea. I think that this would be more suited for larger screens though. I will make a note of this idea. There already is an option to start gestures from the screen edge for both URL bar and sidebar.
I haven't used xScope in years and it doesn't run on any of my devices. I think that if you give Naked Browser some time (about a week) you'll start to become accustomed to the menus. If you can get past the frustrating phase I think that you may find that the menus are very efficient. Of course, if the gesture sensitivity is wrong for your device then that's a different story. I really need to check this out.
Double-tap and swipe to change tabs shouldn't cause much of a performance problem (although I'd have to try it out to know for sure). I was going to allow customizations of this sort of thing in the pro version. For example, double tap and swipe to go quickly to the very top or bottom of the web page. The volume buttons could be used in the same way.
Thank you for the feedback. I appreciate it!
I figured out where the zoom buttons are. They're in framework-res.apk/res/drawable-xhdpi.