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..
Guys,
My GTab is acting weird when I tried some games like Heavygunner, Krazykart and a few others.
The problem is that this games works in landscape mode but it seems that the picture keep spinning to the right and only stop if i put the tablet in portraid mode.... but again the picture still on landscape.
I am making myself clear?
For example: Krazykart... the game shows in landscape but for the car stay steady i have to put the tablet in portraid but the game is running on landscape.
I tried to go to settings and uncheck the g-sensor but no luck... all that does is take off the ability to control tilting it.
Is not on every game that this is hapening and funny is i have another tablet without g-sensor and this games works fine.
Is anybody have the games that I mention above working on gtab with no problems?
If you do, can you tell me where I can download and what version (rom) are you using?
Btw, I am using sotck (the latest version) because wife like it...
Appreciated any info.
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.
The new FPse update is not as smooth a prcoess to update as usual, since you have to either disable your previous settings or clear data out to get the virtual controls to show up.
Another issue is the scaling options are gone, so I can not figure out how to adjust the display. It supposed to be able to be adjusted, but I have yet to figure it out. Everything is distorted full screen now on my Droid 3, Flyer and Thrive. I try to adjust it, but now controls show up. Tried pinch and zooom, in case that was it. Since not working on three devices, seems it is the app rather than the user..... Ok, it could be the user, but no luck on three devices.
Anybody figure it out? Scaled display is better, since no distortion and less pixels for the emulator to draw to (it is faster when scaled).
How to change Nvidia Shield Tablet K1 Resolution from 1920x1200 to 1920x1080?
Basically they have this feature built in if you connect the HDMI cable to the tablet... then the tablet reboot in 1920x1080 and displays only on the HDMI screen (the tablet screen is off)
When you disconnect the HDMI cable it drops a notification every 1-2 minutes do you want to reboot back to normal 1920x1200 resolution and it keep asking till you agree and reboot.
My question is how i can turn it to 1920x1080 or just how to disable the notification that pop up over the screen?
I prefer not to root the device if its possible.
Nvidia Shield Tablet K1 working on Android 6
Thanks.
Hi, came across your question wile looking for a solution as well. I do have a work around for the constant ask for revert from console mode. But not sure if it works on Android 6. I'm on 5.1 still. Hate 6. I do the Console mode remove HDMI thing. Then I go on a rampage force stoping EVERYTHING I find running. I go to Settings/App/Running and force stop everything. Then the Show cached processes, also stop everything. (and I mean Everything I see, including all those google thing I dont need running at the time, tho most will turn themselves on again) Then to the 'All' apps tab and look for everything Nvidia/Shield related and force stop it. And it works. The nagging stop. I haven't figured out what is it that stop the message as I did this once on a rage for that stupid message and since it worked I do it like that every time. And I've play for well over 2+ hours without the message popping up
Oh, also, I don't have a controller but I have All-In-One Toolbox, that I also run to close everything after all the force stops. Just in case. Well with that app you can have a toolbar on the notification and add a 'Recent app' there. Which you can not only use to switch but if you tap it and then tap somewhere NOT on other apps you get send to Home screen. (Wish the add Home/Back as well)
I know it seems like a hassle. I only do this when I want to record something on Ultra and get 1920x1080 instead of that horrid 1728x1080.
OH! And the touch accuracy gets worst the closer you get to the upper/lower borders (on landscape) due to touch screen reading the 1200 pixels on a 1080 shrunk image. Takes some getting used too, but worthy to capture on an OCD friendly video resolution.
I'm on Stock 5.1.1, not root.
Gonna look for a ROM that can do 1080p and also keep the Navbar. And maybe even add 1 tap Screenshot/record shortcuts for the navbar. Old cheap tablet used to have that screenshot button on the nav bar. Which was awesome for quick snap at those special gaming moments.
Anyways, since you have 6, try going Settings/Apps/All and force stop everything Nvidia/Shield related. And let me know how it works. Running apps 5.1.1 management is one of the things that keep me on in. And how micro SD works.
Hope it helps.
@FreelancerGamer
Resoluition:
Root, terminal emulator, commands(enter):
su
wm - displays options
wm size - displays current res.
wm size 1080x1920 - it will change yours res. Restart.
All this things you can do with adb, without root.
Notifications&popup - go to - settings - sound & notify - applications - disable what you want.
Omizuke said:
Hi, came across your question wile looking for a solution as well. I do have a work around for the constant ask for revert from console mode. But not sure if it works on Android 6. I'm on 5.1 still. Hate 6. I do the Console mode remove HDMI thing. Then I go on a rampage force stoping EVERYTHING I find running. I go to Settings/App/Running and force stop everything. Then the Show cached processes, also stop everything. (and I mean Everything I see, including all those google thing I dont need running at the time, tho most will turn themselves on again) Then to the 'All' apps tab and look for everything Nvidia/Shield related and force stop it. And it works. The nagging stop. I haven't figured out what is it that stop the message as I did this once on a rage for that stupid message and since it worked I do it like that every time. And I've play for well over 2+ hours without the message popping up
Oh, also, I don't have a controller but I have All-In-One Toolbox, that I also run to close everything after all the force stops. Just in case. Well with that app you can have a toolbar on the notification and add a 'Recent app' there. Which you can not only use to switch but if you tap it and then tap somewhere NOT on other apps you get send to Home screen. (Wish the add Home/Back as well)
I know it seems like a hassle. I only do this when I want to record something on Ultra and get 1920x1080 instead of that horrid 1728x1080.
OH! And the touch accuracy gets worst the closer you get to the upper/lower borders (on landscape) due to touch screen reading the 1200 pixels on a 1080 shrunk image. Takes some getting used too, but worthy to capture on an OCD friendly video resolution.
I'm on Stock 5.1.1, not root.
Gonna look for a ROM that can do 1080p and also keep the Navbar. And maybe even add 1 tap Screenshot/record shortcuts for the navbar. Old cheap tablet used to have that screenshot button on the nav bar. Which was awesome for quick snap at those special gaming moments.
Anyways, since you have 6, try going Settings/Apps/All and force stop everything Nvidia/Shield related. And let me know how it works. Running apps 5.1.1 management is one of the things that keep me on in. And how micro SD works.
Hope it helps.
Click to expand...
Click to collapse
Hi,
Thank you for your reply.
I tried to force stop but it still pop up the notification to restore to 1920x1200.
About the Android 6, I love it Because of the SD format that turns your SD to be a part of your device storage.
I have a controller so i can navigate even without the nav bars
If i will find something i will update here.
dzidexx said:
@FreelancerGamer
Resoluition:
Root, terminal emulator, commands(enter):
su
wm - displays options
wm size - displays current res.
wm size 1080x1920 - it will change yours res. Restart.
All this things you can do with adb, without root.
Notifications&popup - go to - settings - sound & notify - applications - disable what you want.
Click to expand...
Click to collapse
Sorry for my noob question but can you please explain in more details how i can do this?
More? It's joke? There is no details.
https://youtu.be/84srsYuvKUo
dzidexx said:
@FreelancerGamer
Resoluition:
Root, terminal emulator, commands(enter):
su
wm - displays options
wm size - displays current res.
wm size 1080x1920 - it will change yours res. Restart.
All this things you can do with adb, without root.
Notifications&popup - go to - settings - sound & notify - applications - disable what you want.
Click to expand...
Click to collapse
Thanks for this post, it was answer to what I wanted to do with my tablet - getting full screen for HDMI output without console mode, which frankly would be actually worse even if it did't puck up with my Dualshock 3 (console mode for some reason closes/disables the DualShock 3 connection with the sixaxis app from Play Store) - when using Mirror mode I can use my Dualshock 3 fine and using terminal before starting to play makes the screen look glorious, especially with games like sonic 2 android or Final Fantasy IX android.