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..
Anyway to stretch out apps to fill the whole front screen?
Edit: never mind I figured it out... I didn't know the screens worked independently so the setting from the Inside screen doesnt necessarily reflect changes on the outside screen
Samsung goodtools from their store
I don't know if it's been like this the entire time I've owned the Z Fold 2, but I noticed my screen shifts all the way to the left or right to avoid the hole punch. When I go the full screen apps and try turning off the "hide hole punch" under advanced options, it's already turned off. Switching it on and off again doesn't do anything. The only thing I've done recently was enable Developer Options so I could change the screen width. Can someone please let me know how I can get my apps to fully stretch across the screen and not hide the hole punch?
I have the same issue. There are various options that should fix this, but don't.
* In settings, display, full screen apps, turn on the apps you want to use the full display.
* In the task changer, long press the icon for your app, choose change aspect ratio.
* In good lock, multistar, I <3 Galaxy Foldable, set aspect ratio for each app, set your apps to full screen.
You should try these, one (or multiple) of these options should fix it, but haven't for me.
Only some apps won't go full screen in landscape, but among those are chrome, outlook, kindle, whatsapp. Basically all my most used apps. Other apps use the full screen.
If someone has a working solution, I'd love to hear it.
Thanks! I've tried those options you suggested, however they did not work for me. I feel like I was getting the full screen in the app prior to today, but maybe I'm imagining it. I don't like the way the screen shifts everything over to hide the punch hole. I feel like I may as well kept my Fold 1 with the huge notch because I'm still losing all that space.
So am the only one noticing that all apps are now shifted away from the hole in landscape? The advanced setting to hide the hole is already off and when I turn it on and back off, I can see the screen moving back but then it goes back to hiding the hole even when turned off. Rebooting my phone doesn't fix it.
I've tried a generic Google search with no luck, it always takes me to threads of people talking about it being a simple check box under Settings but they're talking about their phones. My touchscreen was absolute **** when it had a screen protector on it, now it's just **** w/o it. I try to drag and drop an app in the app bucket...app opens instead. Try doing split screen apps, instead the app opens, closes from swiping it sideways vs opening in split screen and or doesn't do anything because it's confused. Sometimes I'll get it on the 1st try, sometimes I'll get it on the 10th when I've already balled a fist and about to punch the thing. Any advice?
So I can't explain what I did to cause this problem as it occurred while I was sleeping and apparently on top of my phone and the screen was not locked, so I hope someone will have some idea of what I did so I can undo it.
So when I woke up and looked at my screen the layout bounds were showing and anytime I touched on anything it was as if my phone screen were moving in slow motion. So I made my way to my developer options and turned off show layout bounds hoping it would fix everything, but all it did was fix that it still continued to move slow and still is a week later and it's driving me crazy. Like when I swipe to open my notification bar or my app drawer it very slowly slides out. It doesn't affect games or when I'm on an app only my phone settings and menus and screens. Anyone know what I may have done to cause this or know how to fix it?
ZooLolly said:
So I can't explain what I did to cause this problem as it occurred while I was sleeping and apparently on top of my phone and the screen was not locked, so I hope someone will have some idea of what I did so I can undo it.
So when I woke up and looked at my screen the layout bounds were showing and anytime I touched on anything it was as if my phone screen were moving in slow motion. So I made my way to my developer options and turned off show layout bounds hoping it would fix everything, but all it did was fix that it still continued to move slow and still is a week later and it's driving me crazy. Like when I swipe to open my notification bar or my app drawer it very slowly slides out. It doesn't affect games or when I'm on an app only my phone settings and menus and screens. Anyone know what I may have done to cause this or know how to fix it?
Click to expand...
Click to collapse
Hi ZooLolly, it would be easier to help if you share some attacments( I mean a small video clip if allowed here).
ZooLolly said:
So I can't explain what I did to cause this problem as it occurred while I was sleeping and apparently on top of my phone and the screen was not locked, so I hope someone will have some idea of what I did so I can undo it.
So when I woke up and looked at my screen the layout bounds were showing and anytime I touched on anything it was as if my phone screen were moving in slow motion. So I made my way to my developer options and turned off show layout bounds hoping it would fix everything, but all it did was fix that it still continued to move slow and still is a week later and it's driving me crazy. Like when I swipe to open my notification bar or my app drawer it very slowly slides out. It doesn't affect games or when I'm on an app only my phone settings and menus and screens. Anyone know what I may have done to cause this or know how to fix it?
Click to expand...
Click to collapse
developer options > window animaiton scale > transition animation scale and animator duration scale = All 1x