Database Info

JF1.41 Bug? changes the way the touchscreen works?

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..

Touch Capacitive Panel (bottom pad)

Hello to all, am going to ask if anybody of you have a problem in TPs Touch Capacitive Pad? I used this app
Nav Debug Tool by HTC
http://forum.xda-developers.com/showthread.php?p=2511016
To check out this multi touch stuff in my TP (though I know before that it has a multi touch feature, I just want to check if it's working properly) but it seems that the pad has a problem. The problem was sometimes, it can register my touch and most of the time, not.. sometimes it can register the multi touch, and most of the time, not .. even the nav wheel has a problem which doesn't register the rotation most of the time. Is this a common problem in TPs or even Diamond??
I even use the signed os WM6.1 but still has a problem.. so I wonder if any of you guys having the same..
thanks!

It's been happening to me for about a year already as well. Seems like it's just defective. It resets thought after sleeping the phone and waking it. I'm not sure if it was because I used to use Sensor scroll or it's a little scratched up.

I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?

R^7Z said:
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
Click to expand...
Click to collapse
that made sense but why would HTC permit a buggy front pad???

You know, it seems many phone brands/cooperations come under fire due to lack of something or another; maybe proof of concept? Perhaps the debug tool is to blame? Or even the sensor degradation over time? One can only speculate so far before it becomes a volatile thought... Again, I point out the idea being good, conceptually. So, I don't know where that exactly puts us as being end users? Then again, I've never really had a decent experience with phones, much less with newer phones; my thoughts and expectations may be slightly on the negative/lesser side of things because of this.

I have the same issue. I used to use GScroll to flip pages in e-books, but finally it got so buggy I had to dump it (other GScroll features were almost impossible to use). I've used NavPad DBug. What I do find is that running the compact heaps command of SK Tools will temporarily fix things, at least most of the time. When I have NavPad DBug running, if it's logging compact heaps will clear out the traces. Somehow or other, it cleans things out when the nav pad gets confused or overloaded with inputs. But even compact heaps doesn't work all the time.
It would be sweet if the capacitative area really worked, but unfortunately it appears to get worn out about the time that you figure out all the things you can do with it. Lol.
Edit: I wonder if the device has problems distinguishing a single touch of your finger vs. several touches. That could really screw up the function of the device.

Why slide to the right to unlock?

I'm kinda old fashioned but I still use an HTC Desire with the original ROM (and living and suffering with its issues) and couldn't move myself to flash it with a custom ROM, because they all seem not to fit my needs. It may sound weird, but here is my thinking about the Android UI development:
Back than, when I bought my Desire it was the best Device of its class out there. The Sense UI was way better than the native Android (which was really ugly) and very comfortable. Since then Android developed to Holo, Sense made several big and weird changes up to the latest one on the M8 and TouchWiz I never liked; and I still think the old Desire Sense UI is one of the best out there. The main reasons for that seem a bit ridiculous but are a major usability issue for me:
Unlock with a slide to the bottom
While receiving a call, slide to the bottom to accept, slide to the top to decline
Two separate lock screens, one as keyboard lock and one as security lock (with password or pattern) that only activates after a set amount of time (not like the Samsung devices where you have to enter your pattern EVERY time you turned off your display)
Why on new devices it is common that I have to slide to the side to unlock? Sliding to the bottom is the most comfortable movement you can do with your thumb without any danger to let your phone slip and hit the ground. So why it is so absolutely uncommon? And why on native Android you can't move the unlock option to the bottom, where is plenty of space and would also give you the opportunity for a fifth quick access app? In my point of view it would increase usability a lot.
While receiving a call on new phones you have to press a virtual button, but why? With old phones you could feel the right button to accept or decline a call, but with touchscreens you have to look at it first and then touch precisely. But there is no need for that. Even the pressing and sliding the green or red circles is based on hitting the screen on a special area, which is kinda unpleasant for me. With the old Sense you only have to roughly slide up or down from around the middle of the screen, so declining a call without taking the phone out of your pocket works like a charm.
At last the lock screen. I always had to decide between the normal keyboard lock and a pattern (password was never an option) but never get it to work with having the pros of both. I understand that some may find it stupid to have two lock screens, but for me they have different functions and so they work very well together in my workflow. On Cyanogenmod I found an option that seems to give me what I want, but it never worked like my Desire.
Yeah, even when I still use my Desire I have used other phones too (in parallel for work) and I really always missed the listed options of the old Sense UI and hated the strange design decisions made since then. But am I the only one who thinks about that in that particular way or is it me who is too picky? Is there no one else out there thinking the Desire Sense UI was outstanding at that time and still is today? Or is there an app for that I haven't found yet?
Just my two cents.

Software (ease of use, features, etc)

When you hand your phone to granny to take a photo of you, can she get the job done? Rate this thread to express how you deem the OnePlus 6T's camera software. A higher rating indicates that the software is easy to use, fast, uncluttered, and inclusive of advanced features for when you need them.
Then, drop a comment if you have anything to add!

On my offical 48+ hours with the OP6T. Having issues setting up face unlock the phone is keeping me in the loop of entering pin/pattern and not opening the face unlock settings, maybe update or software glitch patch. just reset the phone after a full 39+ hour discharge and recharge of the battery, any help with the issue would be great.

I will give it points for the pro mode but outside of that, I find it could use a few more features. If the V40 camera app comes to the V30, I'm going back to it.

Split screen button is unnecessarily hidden under 3 dots on the multitasking screen. This option should be easy access there could be even a gest available for split screen

g_oral said:
Split screen button is unnecessarily hidden under 3 dots on the multitasking screen. This option should be easy access there could be even a gest available for split screen
Click to expand...
Click to collapse
True. I'm not a Huawei fan but I like their knuckle gestures a lot. Swiping with the knuckle from left to right or view versa enters split screen mode for example.

g_oral said:
Split screen button is unnecessarily hidden under 3 dots on the multitasking screen. This option should be easy access there could be even a gest available for split screen
Click to expand...
Click to collapse
You can set up the split screen shortcut under the navigation 'buttons' ie home button
I set my split screen shortcut as a home button long press

One plus 6T is good rather than other phones in its software and configuration.

Normally my Camera opens "instantly".
I encounter from time to time that my camera takes more than a second to start. It's a really fast phone, so what's the probleme here?

I got used to reliability on my OnePlus 5T. 6T is, well, lackluster. I need to reboot it at least once per day. hyperion takes ages to open and the screen is frozen in the meantime. Bluetooth... I am using 5-6 bt devices, and only 4 are on the list when you change volume. Weirdly, it's the disconnected ones, not the ones I am actually using. Sometimes the sound will just ignore BT and go through the phone speaker no matter what it's set to do - another reboot needed. Last weekend Sygic (satnav) crashed so badly the phone went black. No reaction. After holding all the buttons for 10 sec it rebooted to safe mode. Another reboot to normal, and all my settings, launcher, were gone.
Honestly, I want to love it. I do. But I actually hate it. Too bad I already gave my op5t to my daughter. It was soo much better.

Wow, today it just lost audio on voice calls. Why? Because previously I've been casting to a TV. So when the call came the stupid thing didn't know where to reroute audio. So after a while it decided f**k this, it's probably nothing important anyway.
only fixed by reboot. God I hate this phone!
I'm on stable 10 by the way.

I'm really happy with my OP 6T, just wished the camera was better.
I mean come on the secondary camera is only used for depth effect, so is only active in portrait mode...
The only other issue I have is the ambient display doesn't activate as it should imo, only a "hard pick up" will get it to switch on.

The Quest for the Ultimate Experience (Solutions to Some Pixel Problems)

My 1st smartphone was a Palm Pre Plus (webOS), I got an Android next but Went back to WebOS with an HP Veer. ... Really liked how they implemented gestures properly a DECADE before anyone else. Was using Moto phones for nearly 8 years, really loved the Active Display & Moto Actions (camera flip & chop chop flashlight).
With my Moto Z2 Force dying and Moto basically making garbage or something ridiculously overpriced *cough*RAZR*cough* ... had to look elsewhere.
Got a Pixel 5 a few days ago. I hadn't experienced Android 9 or 10, so 11 is a bit step up from Oreo.
Always on display is pretty cool, not as good as Active Display, but better than the old Ambient Display.
Double tap power button to launch camera will work, although not as cool as flipping (I know 3rd party apps exist to mimic gestures, but I'm trying to keep phone as clean as possible for endurance)
Fluid Navigation Gestures can mimic proper Navigation - I'm sorry but the built in Pixel Navigation needs a lot of work. The Swipe up and hold for recent apps is very frustrating to use.
(Here is a solution to removing the 3 button Nav bar on Android 11 with terminal: https://www.reddit.com/r/Android/comments/irs1eb/hiding_the_3_dot_navigation_bar_on_android_11_root/)
(For reference, I disabled the left swipe bar. Kept the right swipe as a back button [the one idea I like of Google's], Right Swipe bottom edge -> Recent apps; Left Swipe bottom edge -> Back; Swipe up bottom edge -> Home [Just as it was on WebOS and Moto One Touch Nav]
Various Apps allow for "chop chop" for flashlight. Still testing which one is the best solution.
And Many thanks to @Tulsadiver For his work on the ancient 3Minit app to work with Pixel 5 /4a etc. https://forum.xda-developers.com/pixel-5/themes/3minit-battery-3minit-clock-t4177835 He also has a flashable Magisk module to remove Nav bar https://forum.xda-developers.com/pixel-5/themes/clock-mods-remove-navbar-mod-t4177829
With those mods, Battery can be changed to similar to Gravitybox Ring battery style and clock can be moved to center or right (the left clock is very annoying).
Just sharing a few things I've come across many different places. Some of this really just writing here for myself for memory and sharing if it'll be helpful for anyone else.
Cheers!

I bought a cheap Moto G7 Power and realized how much I deeply missed some of Moto's little tweaks. Chop and twist are big ones that I miss constantly. Still trying to get an app that implements it half as well. I'd really, really love if we could get a ring battery indicator around the hole punch to reclaim lost space and move the clock. Another killer feature that the Moto had me convinced was just another part of Android was scrolling screenshots. Deeply disappointed when I went to use it on the Pixel with a newer OS and it was missing.

Why are you finding the swipe up hard to use?
Sent from my Pixel 5 using Tapatalk

somnambulantdead said:
I bought a cheap Moto G7 Power and realized how much I deeply missed some of Moto's little tweaks. Chop and twist are big ones that I miss constantly. Still trying to get an app that implements it half as well. I'd really, really love if we could get a ring battery indicator around the hole punch to reclaim lost space and move the clock. Another killer feature that the Moto had me convinced was just another part of Android was scrolling screenshots. Deeply disappointed when I went to use it on the Pixel with a newer OS and it was missing.
Click to expand...
Click to collapse
Yeah I hear ya. The Active Display / Moto Display was great too. At least on the Moto X / X2, after that it wasnt as good but still better than what any other manufacturer has developed.
I've seen the app "energy ring" which does this, but the dev hasn't added support for Pixel 5 yet (it's been added for Pixel 4a, so I'm hoping support will come soon).
With Magisk and tweaks by Tulsadiver, the clock can be moved to the right, it looks much better.

Davey Dual Sim said:
Why are you finding the swipe up hard to use?
Sent from my Pixel 5 using Tapatalk
Click to expand...
Click to collapse
The swipe up is fine, it's the swipe up + HOLD that bothers me. doesn't feel fluid or natural. One motion should control one action only.

roweboat56 said:
The swipe up is fine, it's the swipe up + HOLD that bothers me. doesn't feel fluid or natural. One motion should control one action only.
Click to expand...
Click to collapse
Interesting, I'm finding it one movement , move up from bottom, then the hold is less than s second
Sent from my Pixel 5 using Tapatalk

roweboat56 said:
The swipe up is fine, it's the swipe up + HOLD that bothers me. doesn't feel fluid or natural. One motion should control one action only.
Click to expand...
Click to collapse
If you swipe up from the bottom about ½cm you don't need to do the hold action. It automatically loads the recent apps screen for me. Any higher and it'll take you back to the home screen without holding.

I just use Button Mapper to turn my volume button into a flashlight toggle when the screen is off. Much faster and works more often than the chop gesture. You can customize other stuff too wtih it. A nice all-in-one app.