How about a handgestures recognition app by using the front camera?
It does'nt have to be complicated to be usefull!
*A simple app that record the biggest movement and the direction it goes by using front cam. -Move your hand to the left in front of the camera to navigate left in a menu.
*Trigged by harware key.
*Just for menu navigation and simple tasks. - To move the marker. -Navigate menus while driving etc..
*Trigged by a system event? Recieve sms. Move hand down do mark as read? Calls?
Just some thoughs. I know we will get some of the feautres in winMo 7, but why wait? Anyone with some spear time?
I 2nd this!
I just read the review for the new SE handsett T707. It has a camera-gesture, for instance you can snooze the alarm by just swiping your hand above the handsett (if it's laying down) or mute calls the same way, configurable.
This should be entirely possible with winmo useing both cameras (preferably the one on the front), all we need is a app. Perhaps there is allready one?
I'm 3rd to this...
This one's pretty cool...
Better if they got configuration like:
If certain program/notification is on (maybe call in or SMS in), the camera is activated by itself.
And also if the phone is faced down (front cam is obstructed so it only get dark image), it auto activate the back cam.
If the back cam is also get dark image (obstructed, maybe the phone is in pocket) it'll activate the flash (if there is any and check if they still get dark image or not, because if you're in the dark room then the camera is getting dark image, so it check if its in dark room or really in the pocket).
Because if you're in dark room, no matter you swipe you hand, it'll get dark image, so with the flash on for certain period of time, the cam can get some image even though its blurry.
Otherwise the program shut itself off and leave the notifications on...
I can see this as cool, but perhaps a bit gimmicky.. I don't really see much use aside from simple tasks until the processors, cameras and RAM can improve drastically.
I'm trying to implement pinch-zoom in an app I'm making and am having issues with the onTouch event. It appears that the pointer up & down actions do not fire immediately, like you won't get a pointer up or down until an action move occurs. So what happens if both fingers hit the screen nearly simultaneously is that the 2nd finger (should be pointer(1)) gets a move action before pointer down is called, making the code think it's a DRAG not a pinch zoom. Anyone else seen this? Anyway around it? Thanks.
*Edit*
I just tried out the dotty app and noticed the same behavior on it. Could it be my phone (EVO w/ custom ROM) or is this just an android issue? I'm really having issues keeping my pinch zoom & drag from acting sporadically because of this.
So this is really noticeable when Im viewing documents in Adobe Reader and trying to move the screen to a specific point or drag the slider to a specific page. When removing my finger from the screen it always registers as a slight motion and sets me off several pages (In a 1000 pg text book) or moves the page from where I wanted to position it.
I have SGS Touchscreen booster on CM9 under Super Optimized but I am trying to get rid of that little motion when lifting your finger up. I know its like that for most Android devices though so I suspect there's not too much to do about it, but iDevices do handle that pretty well in comparison.
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.
This thread was originally pointing out the bad kinetic scrolling for chrome only, but now it seems more than app based. Chrome just seems to handle it worse.
Go into settings > dev options > turn on pointer location. Now start scrolling around anywhere and everywhere. I used the launcher, Chrome, maps, Falcon pro, calendar.
Blue line - the actual point of contact?
Pink line - ??
Purple line - some sort of predictive line? Maybe uses an algorithm based on your actual touch to guess any pre-touch contact and post-touch path?
The PURPLE line goes nuts! It is constantly hooking backwards in the direction where I came from. My paths are always curved, and in many circumstances hook back to form the shape of a jagged pubic hair or a fishing hook. I think this hook is causing a LOT of stuttery, jittery scrolling. Is this happening to anyone else?
Seems like some apps may minimize the hooking such as maps or calender, and other apps follow the full hook and mess up such as chrome. However I can't be sure if it's just in my head or if there really is anything app-based.
This does NOT happen on my Nexus 4.
Anyone know what I'm talking about? Is his happening to anyone else? I can post some pointer pictures tomorrow.
Surely someone else has noticed this before? Seems like a huge deal. I have 2 Nexus 7's in my possession (an original device and a new replacement) and both do this exactly the same way.
I can find no evidence of your troubles. 2 screen shots attached from Chrome one, a diagonal scroll and the other a 2 finger pinch to zoom. Try my example page scan.co.uk