Related
I'm wondering if it's possible to modify the "buffer" between when touch input is detected on a list, and when the list actually begins to move when you scroll. Some discussion from back in December of last year on Romain Guy's blog can be found here: http://www.curious-creature.org/2010/12/02/android-graphics-animations-and-tips-tricks/
A few of the relevant comments:
Kleptine says:
December 4, 2010 at 1:19 pm
@Jay/Kristoffer
It seems to me that one of the more blatant scrolling inefficiencies is the fact that it take a couple hundred milliseconds to detect the scroll action after pressing the ListView. It’s fairly apparent on my Nexus One.
to which Romain Guy responds:
Romain Guy says:
December 5, 2010 at 12:49 am
@Kleptine: this was of course tested with users, and the threshold value was chosen based on the “noise” introduced by simply touching the screen.
The meaning of Romain Guy's comment about the "noise" introduced is unclear to me, but I'm wondering if it's possible to reduce the amount of the buffer for a more immediate response to scrolling on our Incredibles, whether through a pre-compilation modification of the code or even once we've got a ROM up and running.
Perhaps the 'noise' is simply the time at which point your finger makes contact with the glass?
¦*¦HYBRID¦*¦SPEED¦*¦ by ws83
Well, to my best recollection, noise in a photograph is unwanted fuzz/haze. Might mean the same here, meaning that the threshold chosen is to weed out any unwanted/accidental touch input.
Don't take my word for it, been wrong before. Lol.
Sent from my Hybrid using XDA Premium App
Right, but I'd like to know if we can experiment with reducing that buffer and seeing how it effects overall performance--WP7 and iOS track finger motion noticeably closer on the screen without causing unwanted touch input. Whether that's due to something else in the code, like precautionary measures that allow for this higher sensitivity without causing other issues, I'm not sure.
PLEASE HELP - - -Is anyone else experiencing these display problems? &/or have possible solution(s)??
The over the air update seems to have completely cured my data connectivity problems : - }
But my unstable display problems persist and are driving me nuts - Considering a return.
(ON A SIDE QUESTION - - - Has anyone found an alternative browser, such as opera mini, which works on the N L 900? Opera Mini was very adequate on the old WM 6.5 Tilt 2)
(I) In Internet Explorer all pages seem to default to a really tiny type - Absolutly unreadable.
While the type can be enlarged with a 2 finger spread, the increase is very jerky / uncontrolable, and worse yet, moves / recenters the display unpredictibly. Then, with any movement of the phone (even without finger touches on the screen) it resizes, usually reverting back to tiny. Changing the page also resets to unreadable / tiny, and recenters it. So the problem is the web pages are not readable, and any luck in getting it re-sized is almost immediately defeated.
Another aspect of the problem is that with any faint or slight movement, the display page rotates almost at random between portrait & landscape. This also messes up zooming, etc. as mentioned above . . .
This problem also makes it impossible to use the phone to read a newspaper (such as NYTimes.com) because the dynamic resizing does not allow me to easily scan parts of the page to get where I want, and then achieve / maintain adequate zooming to get the whole "column" visible at once.
(II) in Microsoft Excel, a similar problem occurs with viewing & editing spreadsheets. But in Excel the random rotate problem is much more severe. Another aspect is that the zooming / sizing of the spreadsheet page is not stable when moving / panning from one part of the sheet to another.
Together these drive me nuts. Any ideas as to a systemic solution, or do you guys think it is just a fluke of some bad hardware??
Comments appreciated,
Thanks,
Artzznyzz
When reading web pages, double tap to zoom on the text block. A lot of times that's good enough so you don't have to manually zoom.
Sent from my Lumia 900 using XDA Windows Phone 7 App
It almost sounds like you have a hardware problem. My screen is pretty stable. The issue I run into is that certain pages, xda included, will sometimes break apart and be unreadable. parts of the screen start to duplicate over and over all over the screen... I've already re-flashed the stock ROM, and applied the 12084 update, but it's still happening. It never happened on my Samsung Focus.
Yea I have the same problem, its like the browser is having problem rendering/displaying the content, I usually have to reboot the phone to fix it. Anyone else having the same problem? Is it ie9 on WP? Its really annoying, I get it mostly w xda pages.
But my Focus with Mango and IE9 doesn't do it. I notice it most on XDA, just because this is my most visited page on my phone, but it happens on other pages too.
I feel like I had this problem once on xda but I can't seem to replicate it. I have noticed a couple of other sites that render really weirdly though, for example shamusyoung.com/twentysidedtale renders the page titles between the header image and the body in absolutely gigantic font. IE9 on the desktop renders it correctly too, which is what makes this even stranger.
Helps, although not enough.
There was that setting in previous versions, something about Overview. Unchecking it allowed the text to show up much larger....not available in this version...
romeo0119 said:
Yea I have the same problem, its like the browser is having problem rendering/displaying the content, I usually have to reboot the phone to fix it. Anyone else having the same problem? Is it ie9 on WP? Its really annoying, I get it mostly w xda pages.
Click to expand...
Click to collapse
I can third or fourth the screen fragmentation, duplication issue. It seemed not to occur very early on in the firmware life of the phone, but has since made browsing an obnoxious chore. Might it have something to do with cache management on IE9 part with these more difficult to render sites? Ive loaded sites properly upon first visit, only to experience the issue on most subsequent visits.
Also, to comment on the OP's problem, I have read from multiple sources that IE9 for Windows Phone 7 will convert some sites' text size data to pixel values, which causes certain page issues when zooming.
I just reread this OP. I didn't realize we had an over the air update. Hope I didn't miss mine...
Concur ran into a problem yesterday browsing XDA forums on a wifi connection. Screen went 'white'. Scroll bars were still there but no visible text. Selecting other web sites turned up the same result -- clearly the pages loaded (background color changed, scroll bars, loading progress bar complete). Turning the device completely off was the only cure. Have only run into the problem once... unable to reproduce. Browses XDA just fine now.
Cheers
Hi
I have a mysterious problem with one of my applications. For some reason it doesn’t work properly with Samsung Galaxy Tab 2 10' (probably other devices too, this is the only one I’m sure of). Unfortunately I don’t have access to such device and sense I make no money on my application (it’s free) I was hoping that someone here could help me test this .
My application is used for education and is mostly designed to learn foreign languages. One way to practice is to use flashcard that I have implemented in OpenGL. To get this working I render bitmaps with text that is shown on the cards.
One user has reported that this doesn’t work with Tab 2, after a while the text is no longer visible. If the application is paused and then restored it works again. The bitmaps are rendered in a thread and I think that is the problem (if no threads are used it seems to work better). All devices I’m using for testing works fine so I’m really puzzled.
To test this please download and install:
http://www.pekspro.com/vokabelbeta/Vokabel1_13d.apk
Open the application, go to the files and open a file in the examples.
When the file is open, go the the tab Quiz and select Flashcard (3d).
Every second time bitmaps are generated in a thread, other times without any thread. On the top of screen there is some debug text. Please let me know what is says if cards are stopped working. Or even better send me a log from the application.
This feels like a weird request, but please please please help me solve this problem. It literally keeps me sleepless, xda is my only hope .
I can confirm that after a couple of questions, the flashcards go blank.
The debug text doesn't seem to change though
(Alive counter:nnn Duplicate request for: xxx)
It only seems to happen in landscape and it can be cured by rotating to portrait then back again...
In portrait mode the debug in this case is always just 'single thread'.
I would have a go on the emulator set to 10" landscape.
Thank you so very much . This is really interesting information for me.
I have done some testing with the emulator and some other devices but haven’t been to replicate the problem. I have reviewed my code and changed a couple of things that might cause some problems. Do you mind do a second test?
http://www.pekspro.com/vokabelbeta/Vokabel1_13e.apk
Either way I’m really thankful for this
Now the problem is solved. Thanks for all feedback
pekspro said:
Now the problem is solved. Thanks for all feedback
Click to expand...
Click to collapse
OK good to hear.. sorry I didn't notice your second message !
Hello,
I am a french blind and use a Razer Phone, not for gaming but for listening classic music. I am very disappointed because accessibility mode is pitiful. Is there some people who use accessibility mode and what do you think about it?
The gesture of shortcuts don’t permit a complete reading and after a come back to Razer support, the device changed for a little better but since Oreo the reading is disastrous.
Do you known some blind people who use Razer phone?
Thank you,
Best regards
André
verandre said:
Hello,
I am a french blind and use a Razer Phone, not for gaming but for listening classic music. I am very disappointed because accessibility mode is pitiful. Is there some people who use accessibility mode and what do you think about it?
The gesture of shortcuts don’t permit a complete reading and after a come back to Razer support, the device changed for a little better but since Oreo the reading is disastrous.
Do you known some blind people who use Razer phone?
Thank you,
Best regards
André
Click to expand...
Click to collapse
Hey André!
As far as I am aware the Razer phone is mostly stock so any and all accessibility features it comes with are made by google android. I don't believe Razer have added any of their own or removed any from the android builds.
The only phone manufacture that I am aware of which includes any additional accessibility options is Samsung..
I must admit that I am curious as to why you chose the Razer phone as one of it's only standout features over other, better or more suitable, phones is it's 144 hertz screen which I'd image isn't of much use to you.
Sorry to sound a little blunt or be a downer but the impression I get from Razer is that they can barely make a phone for fully able bodies, there are plenty of hardware and software issues so I'd be very surprised if they intend to improve the accessibility of the Razer phone.
I've tried to format this in the hopes that screen readers or translation programs will be able to read it correctly.
Sorry if it's not perfect!
Azure Wren.
verandre said:
Hello,
I am a french blind and use a Razer Phone, not for gaming but for listening classic music. I am very disappointed because accessibility mode is pitiful. Is there some people who use accessibility mode and what do you think about it?
The gesture of shortcuts don’t permit a complete reading and after a come back to Razer support, the device changed for a little better but since Oreo the reading is disastrous.
Do you known some blind people who use Razer phone?
Thank you,
Best regards
André
Click to expand...
Click to collapse
Hi andre.
I am visually impaired. Legally blind but not fully.
I use magnification a lot and i use a navigation bar button to activate the feature.
May you please explain me your needs and what accessibility features you uae?
As mentioned above, the razer phone has a moatly stock android version so "theoretically" there should not be any problem with that. Please respond. I would be glad to help.
Hi,
Thank you for your help proposal about the accessibility feature.
I use the syntesis Talk Back to discover what is displayed on the screen. Theoretically, the accessibility function is native in the Androïd system and should be able to work like all the features built into this system but alas! (three times alas!) There is a malfunction with the Razer phone. To make speech synthesis speak, the blind user uses shortcut gestures.
At first use, the two-finger swipe gesture from top to bottom or from bottom to top permiting to scroll text was inoperative and caused the opening of one unknown link. After a return to the support of Razer Society, his malfunction was corrected. Since the installation of Oreo, the statement of a word or a text is interrupted as a result of a crackle.
Only playback triggered from the accessibility button at the bottom and at the far right of the screen is operational, but other shortcut gestures allowing to trigger playback see their action interrupted by a crackling sound.
Through my email, I hope to find one or two blind users to share their experience with Talk Back and Razer phone voice synthesis. It will be a great pleasure that I will accept the help of curious users who would like to test the accessibility function and Talk Back to know their experience and especially that they confirm playback malfunction when it is triggered off by either shorthand gestures or the general context menu.
I thank you for your help and, perhaps not to disturb the forum, we could exchange directly unless the subject can be developed for the good of all.
In a previous email I declared that I have chosen the Razer phone for these two speakers and also for the system which does not have an underlay other than the android system. My contacts with the support staff are very good but, I think their superiors are not up to it.
I am counting on you since you propose it to me.
To simplify the test, I suggest that once the accessibility function and Talk Back are enabled to perform that you specify the result of shortcuts in the board in the end of my text.
Sorry, I had done a board but I can not join a link because I am a new user of the forum. If you want to help me, I can send the board in a private mail. You can write me at [email protected].
I thank you very much for your help and for the interest you have in the difficulties encountered by a person with a disability.
Best regard.
I am dissapointed with many missing features in oxygenOS and other things like :
1)Screen pinning with gestures is not possible even though google had implemented this quite a while ago.
2)Bloatware like multiple "file" apps and netflix
3)How confusing it is to access emergency contacts through lock screen
4)Users cannot directly login to their account from lock screen by typing their respective password. It takes too much of time in switching profiles.
5)Call recorded filling the view in voice recorder, it should be in a folder when we swipe right in recorder.
6)Lift to wake feature not present.(the app made for this is a hit or miss sometimes and does not work with ambient display, but kudos to the developer)
7)Being switched off easily without passcode so if stolen the thief can quickly get away. ( I know there are other ways but thiefs are not that smart i assume)
8)60fps video is considerably dull compared to 30fps both in hd and 4k.
9)Manual focus does not provide complete range of focus in pro mode, and you can only shoot from main lens in pro. 48mp mode is also hidden there..
10)System software using 27gb of internal storage, would have bought the 256 gb variant if i knew about this.
And many many other countless things i can't remember at the moment but could be improved very easily by oneplus.
Do you agree with me or am i wrong at some places ? This is my first post so don't hesitate to point out my mistakes.
You expect too much, if you were so concerned with such minute things, you might have stuck with your previous OEM
Oneplus doesnt know what you are used to and what you want, they provide what they feel is best, you should have done a through research if you had such needs, also there are barely 2-3 promotional apps which you call bloatware. Also the file app which you say is installed on every android device by default which is triggered when sharing, its just oneplus gave you an icon to access it separetly too.
aryan2708 said:
I am dissapointed with many missing features in oxygenOS and other things like :
1)Screen pinning with gestures is not possible even though google had implemented this quite a while ago.
2)Bloatware like multiple "file" apps and netflix
3)How confusing it is to access emergency contacts through lock screen
4)Users cannot directly login to their account from lock screen by typing their respective password. It takes too much of time in switching profiles.
5)Call recorded filling the view in voice recorder, it should be in a folder when we swipe right in recorder.
6)Lift to wake feature not present.(the app made for this is a hit or miss sometimes and does not work with ambient display, but kudos to the developer)
7)Being switched off easily without passcode so if stolen the thief can quickly get away. ( I know there are other ways but thiefs are not that smart i assume)
8)60fps video is considerably dull compared to 30fps both in hd and 4k.
9)Manual focus does not provide complete range of focus in pro mode, and you can only shoot from main lens in pro. 48mp mode is also hidden there..
10)System software using 27gb of internal storage, would have bought the 256 gb variant if i knew about this.
And many many other countless things i can't remember at the moment but could be improved very easily by oneplus.
Do you agree with me or am i wrong at some places ? This is my first post so don't hesitate to point out my mistakes.
Click to expand...
Click to collapse
2)Netflix: is mandatory to get HDR certification (Netflix mandatory)
6) You have that option under system settings.
7) All phones, computers, servers... All of them can (and MUST) be switched off without password or software related requisite.
10)A/B partitions (Google mandatory). Thanks to that we can participate in beta programs and have quicker updates.
Pantumaca said:
2)Netflix: is mandatory to get HDR certification (Netflix mandatory)
6) You have that option under system settings.
7) All phones, computers, servers... All of them can (and MUST) be switched off without password or software related requisite.
10)A/B partitions (Google mandatory). Thanks to that we can participate in beta programs and have quicker updates.
Click to expand...
Click to collapse
In samsung mobiles, you are required to put the password before switching off the phone. So i wish that could also be implemented in oneplus.
The lift to wake feature i want is when I pickup the phone, it completely unlocks after seeing my face which is not present.
I wish i also knew about the 27gb thing cause then i would have bought the 256 because overall the phone is great.
Ik i am nitpicking but some points are still valid.
aryan2708 said:
In samsung mobiles, you are required to put the password before switching off the phone. So i wish that could also be implemented in oneplus.
The lift to wake feature i want is when I pickup the phone, it completely unlocks after seeing my face which is not present.
I wish i also knew about the 27gb thing cause then i would have bought the 256 because overall the phone is great.
Ik i am nitpicking but some points are still valid.
Click to expand...
Click to collapse
About Samsung mobiles, I guess you are talking about normal switch off. There is an emergency switch off (vol- + power)that should overrides any pin (in any manufacturer).
Ok, you mean get into home screen. Well, that is a personal preference. I prefer to stay into lock screen but with the notifications expanded to see if I really want/need to unlock the phone.
The space used by the system is that way since android 9. All we know that android is about 10gb so if you have two partitions (A/B) it will be twice the space used. All manufacturers warn about it into the specs with something like "the space available for the user will be less due to blablabla...".