Database Info

Keyboard lag "fix"

I just found this website with a fix for the keyboard lag in the stock browser:
smartadopter Wordpress -> TIP Improve Honeycomb Browser Speed
(I am new so not allowed to post outside links )
Basically it says:
1) as url type: about:debug
2) nothing will seem to happe.n BUT new menu options are available now
3) go to menu -> settings -> debug, and uncheck OpenGL Rendering
4) no more lag!
If this already floated around this forum, sorry. But if not, or for the people (like me) who missed it, enjoy!
I have not found any drawbacks of this fix. But if anybody find/knows any drawback/problem with this, please let me know.

Ill test this but im guessing scrolling speed will suffer as that uses the OpenGL.
Sent from my HTC Desire S using XDA App

Good advice. Will try it out now.
Tested and it works great. Scrolling is not affect either by this by the looks of it. Zooming works as well.

This fix isn't working. The input lag isn't gone completely, it's less noticeble, but it's still there.
And like someone mentioned before, scrolling isn's as smooth as before. Also YouTube videos don't work.

All this fix does is turn off hardware acceleration in the browser.
Some things get better, others get worse.
sassafras

Scrolling is not as smooth but I have no problems displaying YouTube movies.
But typing is a lot easier without (or with much less) lag.
So for me OpenGL rendering will stay off until the next update.

And lose my graphic acceleration? No thank you

No drawback?! Scolling looks like a freaking slideshow with that disabled ^^

Quick question for you guys... does the keyboard lag in Dolphin HD?

Not as much as the stock browser.

henkyie said:
I have not found any drawbacks of this fix.
Click to expand...
Click to collapse
For me the drawback is very obvious ... scrolling through a thread in this forum is horribly slow without OpenGL. But the keybord works like a charm.
I think, I will stay with Opera for forums and use the stock browser for the rest with OpenGL switched on ... loading times in Opera are much slower.
Thanks for the tip though.

I notice objects on the page rendering with every swipe as I move down the page ...probably why scrolling is not as smooth.

Strangely the scrolling lag has disappeared. So now I have less typing lag and little scrolling lag.
So until the next update I am a happy camper.
The only lag in typing I have left has to do with the auto complete function of the on screen keyboard.

This warrants further study (in the words of someone famous) because I'm seeing the exact opposite effect.
I've gone back and forth between this site and another forum having a similar javascript textarea form, comparing text entry with the "Enable OpenGL Rendering" box checked and unchecked in the Debug menu. On both sites, text entry is WAAAY faster using the dock keyboard with the box CHECKED. This is using the stock browser, BTW.
If I use a virtual keyboard (Swype for tablets in my case), it's still faster with OpenGL enabled but not nearly as fast as with the dock keyboard.
There must be some other factors involved however, since this behavior is not consistent. At times the keyboard (dock and virtual) seriously lags regardless of the Debug setting.
I sure hope Google (or ASUS) can fix this issue since it's hugely frustrating when the keyboard lags badly. In a few cases, I've just given up trying to post a message and pulled out my laptop instead of fighting the browser.

[APP] PDF Viewer update

I needed a PDF viewer for my own purposes, and the closest I could find was Maciej's PDF Viewer (=apv) app on the market. It was open source, and so I made a bunch of changes that I wanted or needed. Anyway, I now have a pre-release for version 0.3.0, which include a bunch of enhancements since Maciej's 0.2.9 release.
Here it is.
New features:
- speed optimizations
- page number display
- options including: full screen, reverse video, various tweaks, page with volume keys
- overhauled file selection: added icons for directories, added home directory option
- better font rendering

Now I posted pre-release 0.3.0 pre 2. Includes a monochrome feature to save memory and a zoom-to-width feature which I think people will find handy.

Sounds like you know what your doing. Not had a chance to test your app yet, but does it have the functionality to add bookmarks and highlight text?

Gonna try it out now, thanks!

No, there is no annotation, sorry. Just reading.

Its really nice with open source alternatives. Im gonna try it out.

I think i will love this. thanks bud

I haven't tried it yet but it would be great if you could add zoom to a fixed percentage
the reason I want that is some pdfs have huge fonts for the page numbering and while technically fit to width is working, there's still a fair amount of room on the sides. Obviously this should be sticky. A bonus would be it would remember the setting by filename

Works good, one option I'd love to get is fixed scrolling like with browsers

sark666 said:
I haven't tried it yet but it would be great if you could add zoom to a fixed percentage
the reason I want that is some pdfs have huge fonts for the page numbering and while technically fit to width is working, there's still a fair amount of room on the sides. Obviously this should be sticky. A bonus would be it would remember the setting by filename
Click to expand...
Click to collapse
Zoom settings are indeed remembered by filename.
You can also adjust how much the zoom buttons zoom by. If you set that to 5% or 10%, you can do zoom-to-width and then press the zoom button once or twice.
Eventually, I'd like it to detect the real edges of the text.

moav said:
Works good, one option I'd love to get is fixed scrolling like with browsers
Click to expand...
Click to collapse
I couldn't figure out how to implement that. Moreover, I find it's poorly implemented in the browser--it locks much better on my device into horizontal movement than into vertical movement!
Instead, there is a "vertical scroll lock" option. This locks the scrolling to be only vertical, unless you make a serious (1/5 screen width) swipe left or right which temporarily unlocks horizontal scrolling.

I`ve just tested this app for half an hour with a bunch of PDFs littered in my Desire. This is without exaggeration the best pdf-viewer I´ve seen so far.
Very useful:
- zooming in steps as little as 5% because most PDFs were made for monitors or printing and not smartphones
- inverting the screen for reading at night or low-light conditions. It also saves power on my screen to read white text with black background.
- and it´s FAST
What I miss:
- an option to forget about the layout of a PDF, so I can only get the pure text. This would be very useful for PDFs designed for magazines with a columned layout, which is a pain to read on a handheld computer.
Keep up the good work

germanhoss said:
I`ve just tested this app for half an hour with a bunch of PDFs littered in my Desire. This is without exaggeration the best pdf-viewer I´ve seen so far.
Very useful:
- zooming in steps as little as 5% because most PDFs were made for monitors or printing and not smartphones
Click to expand...
Click to collapse
Remember, too, that if you set the 5% zoom option, you can still long-touch the zoom buttons for a 2X zoom.

arpruss said:
Remember, too, that if you set the 5% zoom option, you can still long-touch the zoom buttons for a 2X zoom.
Click to expand...
Click to collapse
Wow, haven´t noticed that - that´s quite useful.
Originally I thought of requesting a feature to remember the place where I closed the document because I´m used to open things in the ES explorer.
Then I stumbled through the built-in file explorer - feature implemented
Maybe an FAQ or a short manual would be useful ...

germanhoss said:
Wow, haven´t noticed that - that´s quite useful.
Originally I thought of requesting a feature to remember the place where I closed the document because I´m used to open things in the ES explorer.
Then I stumbled through the built-in file explorer - feature implemented
Maybe an FAQ or a short manual would be useful ...
Click to expand...
Click to collapse
There is a wiki on the project page. You can add a FAQ.

It's a great light app and it has some cool features which I miss on other apps. But my primary feature for PDF readers is smoothness.
It would be great if it would be working as smooth as Documents To Go (their PDF reader). By smooth I mean smooth rendering and scrolling. Also it won't hurt to have multitouch zooming.
I know it's easy to demand and hard to do but at least there are ideas what should be present in the next versions.

jankoboys6 said:
It's a great light app and it has some cool features which I miss on other apps. But my primary feature for PDF readers is smoothness.
It would be great if it would be working as smooth as Documents To Go (their PDF reader). By smooth I mean smooth rendering and scrolling.
Click to expand...
Click to collapse
That's largely a matter of speed, and it's going to be hard to improve that, except by expending a lot of memory for caching and background rendering.
Also it won't hurt to have multitouch zooming.
Click to expand...
Click to collapse
I agree, but it is a finicky feature to implement correctly and hence requires a multitouch device for debugging. I don't own one. Moreover, there are potential patent issues.

I've just posted 0.3.0 pre 13. This unfortunately has a new bookmark database, not compatible with previous versions, so people will lose their per-document settings. I am hoping this is the last such loss--the new format will make code maintenance easier and is easily upward expandable.
New features/fixes in pre 13:
- store horizontal offset in per-document settings
- better restore of zoom if orientation has changed
- fix round-off error which resulted in occasional horizontal one-pixel-width errors

I would also like to mention the color feature in your app is really great! Now I can read without hurting my eyes in the dark and it saves batter as well. Great feature indeed!
arpruss said:
That's largely a matter of speed, and it's going to be hard to improve that, except by expending a lot of memory for caching and background rendering.
Click to expand...
Click to collapse
hmmm what if you make the memory size for caching an option in the settings for users to choose their optimum size? Do you believe that this would make any speed improvements?
arpruss said:
I agree, but it is a finicky feature to implement correctly and hence requires a multitouch device for debugging. I don't own one. Moreover, there are potential patent issues.
Click to expand...
Click to collapse
I see it's kind a hard/expensive to make this feature possible. Darn US laws on patents :-/ don't know if in EU is the same for Android apps but for C++ and other programming languages, there are no e-patents.
Keep on your great work!
PS: I'm using HTC Desire (CM7 rom)

jankoboys6 said:
I would also like to mention the color feature in your app is really great! Now I can read without hurting my eyes in the dark and it saves batter as well. Great feature indeed!
hmmm what if you make the memory size for caching an option in the settings for users to choose their optimum size? Do you believe that this would make any speed improvements?
Click to expand...
Click to collapse
Maybe, but it would need a smarter pre-render queue than we currently have. I experimented with making one, but my attempts were buggy so I got rid of them.
Tell me which scrolling pattern you'd like to be faster? Currently the app (in render ahead mode) is optimized for ebook reading: you read a page, and while you read the page, the next one is rendered and shows up instantly when you flip pages (I generally do that with the volume-down key) or scroll vertically to it.
Unfortunately, there seems to be a bug somewhere, perhaps only on devices with larger screen resolutions (it works fine on my 854x480 Archos, but I am told that it doesn't work on a 1280x960 screen), which makes the next page not show up instantly.

240 dpi Contacts(Dialer), Touchwiz Calculator and S Planner (Request)

Anyone can try to mod Contacts(Dialer), Touchwiz Calculator and S Planner and even Wall Paper changer to work with 240 dpi or even less dpi on Note?

I second this...
Im using 3rd party dialer, but i wish i can have those native apps in the lower density.
Sent from my GT-N7000 using XDA App

I would love it !!!

danilos2k said:
I would love it !!!
Click to expand...
Click to collapse
I followed your advice given on Androidiani and 240 dpi are looking lovely.

danilos2k said:
I would love it !!!
Click to expand...
Click to collapse
+1

I would like to see this, too! Would be very nice!

i would love to have automn dialer ....have a look..
http://forum.xda-developers.com/showpost.php?p=19927125&postcount=6

i want this too, ive gone below 240 but 240 seems to be the sweetspot before the battery icon starts to blur. i also use 3rd party dialer i use angel dialer so i never see a problem. but it would be nice to have the native dialer work.

Does S Memo work for any of you when you use anything other than 320dpi? I get thick lines running across my notepad with anything other than 320.
edit: I just found the modded s-memo thread. Now all I need is the rest!

maybe a weird question, but why less dpi?
What changes are needed, just apps?

OpenMinded said:
maybe a weird question, but why less dpi?
What changes are needed, just apps?
Click to expand...
Click to collapse
If you tell the phone that the screen has 240dpi instead of 320, then it starts drawing things smaller. For instance, 12pt fonts are used instead of 16pt, or the icons become 30x30 instead of 50x50.
As the phone uses the pixel density information to calculate how many pixels should a quarter-inch-wide icon should be, coding in a lower dpi value makes all the drawn elements smaller, giving you more room. This way, you can have smaller text and have more on our gargantuan screen.
Most apps deal with this change nicely, as there are devices out there that actually have 240dpi density. A number of apps (google market) need your pixel density to be one of the supported ones (180,240,320) and other arbitrary values break certain app updates. And some apps (mostly samsung-specific ones) have hard-coded scaling factors that break the app when you change your density setting.
All in all, decrease the density value => have everything rendered/drawn smaller => more screen real estate, the caveat being a small number of apps not supporting scaling at all.

awesome explanation, I 'hit the button' .
Thanks.
To be honest I am happy with the space and prefer the 'no hassle' approach .
So apps that do not support scaling would simply not be in fullscreen mode?

OpenMinded said:
awesome explanation, I 'hit the button' .
Thanks.
To be honest I am happy with the space and prefer the 'no hassle' approach .
So apps that do not support scaling would simply not be in fullscreen mode?
Click to expand...
Click to collapse
It would make sense for the unsupported apps to simply be smaller than fullscreen, and it certainly is the case with samsung's touchwiz dialer, where it sits close to the upper left and has unused room on the right and bottom (contact list, call log and favorites tabs of the phone app scale nicely though).
On the stock launcher (touchwiz, samsung, surprising?), the dock is still at the very bottom of the screen, but there is unused/unusable space between the dock and where your app icons sit. third-party launchers (I tried adw ex) have no problem dealing with scaling.
For the s-memo app, it gets funkier, as the background drawing part of the code seems to have some weird hard-coded scaling, and when you increase your density, the memo-drawing area both shrinks (like the dialer) and also has thick black horizontal lines on it. Looks like an aliasing effect.
So it depends on how the various bits and pieces of the UI elements are coded in each app. If they coded it with multiple densities and scales in mind, it works like a charm. If they ignored it, it depends on where the reference/anchor points of UI elements are, as things can all get scaled and shrunk towards the upper left, or some things may stay at the bottom while others shrink towards the top. If the coders dropped the ball completely (s-memo), things get very ugly.

Hope this thread won't be ignored... Looking forward to some kind fella who would probably get this working

stephenjason89 said:
Hope this thread won't be ignored... Looking forward to some kind fella who would probably get this working
Click to expand...
Click to collapse
Would be very, very nice!

up for this

ignored for a long time

KL7 and beyond dialer is especially dreadful at 240 dpi, since the call button is effectively hidden

I'm going to attempt to follow this tutorial myself:
http://forum.xda-developers.com/showthread.php?t=863519

crysalis786 said:
I'm going to attempt to follow this tutorial myself:
http://forum.xda-developers.com/showthread.php?t=863519
Click to expand...
Click to collapse
Please share if you have succeeded.
Many thanks!

[Q] "My ASUS lags on this game" how to down the resolution

Hi guys. Lets say I have a game or app and it lags cause of 1080p. (DO NOT answer like: This is not the resolution problem, because sometimes it is). Or just app is not supported by full HD. Anyway. Can I change the resolution for 1280x800 (Popular and from normal Transformer)? Does simply DPI change work? What to set? Please tell me. Just for the situation with 1280x800, I want ALL apps etc to run in this resolution. Will it lag anyway?
Sorry for my English.
This thread is duplicated, please delete one.
http://forum.xda-developers.com/showthread.php?p=32100258#post32100258

Actually this is a pretty good question. Some games can't really be displayed in full HD because it just requires much better hardware than is in our devices. Lowering the resolution would probably be very helpful in improving the frame rate and consequently the game play.
Sent from my ASUS Transformer Pad TF700T

I'd like to know an answer to this too. Is there a simple way to do this, such as installing an app from the Play Store?

perhaps paranoid android can help?
http://forum.xda-developers.com/showthread.php?t=1904894
have not tried it myself.
I don't know of any app or setting that does what you want.

changing the dpi will do nothing to change the resolution. all that does is tell the OS the physical size of the pixels on the screen in an attempt to keep UI elements the same size across varying dpi screens.
for example, if you take an icon and display it on a regular screen and an hdpi screen with a straight 1:1 pixel mapping, it will appear much smaller on the hdpi screen. but if you tell the OS what the pixel density of each screen is, it then has a reference point and can then enlarge or shrink the icon so that it appears to be roughly the same physical size on both screens.
this is why lowering the dpi setting on your device shrinks everything. the OS thinks the pixels of the display are much larger than they are and shrinks the images to make them appear the intended size.
to change the display resolution, you'd first need a display driver that supports the lower resolutions, which we seem to have since we can output at 720p over hdmi. then you need a screen that will upscale lower resolutions to fullscreen (because you really don't want to play in a tiny 1280x720 window do you?) when non-native input (something other than 1920x1200) is received. i'm not sure if the display in the infinity is built to do that. they may have designed it thinking they will never run it at anything other than native resolution and left it at that.

who said anything about dpi?

Transformer TF300 update on TF700
Happily we have previous Transformers with almost the same hardware and lower screen resolution. Do I have FULL HD installing this (UP) ? I guess gaming on tablet with lower resolution is not possible, but maybe I can downscale the graphics with CHAINFIRE 3D. This is really cool feature. I think we all need it (now and in future). 1280x800 is acceptable res, and some games just won't work on FULL HD.

lafester said:
who said anything about dpi?
Click to expand...
Click to collapse
Uhh, the OP?
LEGOracer69 said:
Does simply DPI change work?
Click to expand...
Click to collapse
Sent from my ADR6425LVW using XDA Premium.

lafester said:
who said anything about dpi?
Click to expand...
Click to collapse
the op did. durrrrrrr
read much?

Internet browser's window resolution is only 1280x710?

In comparison with my laptop's 1080 and my desktop monitor's 1440 resolutions, the highest of all resolutions - my tablet has upsetting low resolution when I browse sites.
Any way of increasing it at least to 1080?

What makes you feel that the resolutions is low? The amount of info shown on the screen or the actual clarity of the image?
Sent from my SM-P900 using Tapatalk

To make it short: http://whatsmy.browsersize.com/

Maybe stop using Samsung's stock browser?

No, change the dpi setting for the browser using Xpo sedan module App Settings. Setting Chrome to 213 gets me closer to 1080 though not exactly 1080.
Text is small though so I'm not leaving it like this.

I am seeing 1280x800 on both stock browser and Chrome. I am wondering if that is just the browser that rescaled to make it easier to read the text. I will check my GN10 2014 to see it will say the same?

double07 said:
I am seeing 1280x800 on both stock browser and Chrome. I am wondering if that is just the browser that rescaled to make it easier to read the text. I will check my GN10 2014 to see it will say the same?
Click to expand...
Click to collapse
I ran the test on every android device I have, none came above the 750 pixels wide. Which is a nightmare, because all the responsive design sites think anything below 1080 wide is 4" or smaller, so you get forced onto the mobile website with no way to the desktop version (as that's how responsive works, there's no "go to desktop view" and "use desktop mode" doesn't work.)

ShadowLea said:
I ran the test on every android device I have, none came above the 750 pixels wide. Which is a nightmare, because all the responsive design sites think anything below 1080 wide is 4" or smaller, so you get forced onto the mobile website with no way to the desktop version (as that's how responsive works, there's no "go to desktop view" and "use desktop mode" doesn't work.)
Click to expand...
Click to collapse
I misread. The screen size is 1280x800 while the browser is 1280x750 as you mentioned. However, the very strange thing is: The reading seems to vary. I am getting browser size from 1280x688, 710, 750 ???
Using Dolphin browser, the sreen size is 2560x1600 while the browser size is 980x525.
I am beggining to question the the test app? if it is getting the correct info or different browsers are really skew the resolution?
I don't know what to believe at this point?

Blech, I just realized that I had typos in my prior post. Have any of you tried setting dpi in xposed module App Settings yet? I have settled on a setting of 256 and get a browser window width of 1600 on the test site that camspy linked above.
Sent from my SM-P900 using Tapatalk