Database Info

Throttle Launcher

This is a great Today app, but has annoying habit of moving down the screen by a bar - see attached pic. Anyone know solution or not have this problem?

I liked it too... for the first 5-10 minutes or so. Gave it my best shot, tried many settings and options, installed and re-installed it a few times, but it's buggier than an entomology museum and eventually screws itself and your device up.

yep, i agree, funny and eye candy interface but heavy and buggy... i did it a chance but uninstalled soon.
Anyway, i got the same bug... there should be an option in the first tab of TouchFlo settings panel for the plugin heignt, you have to reduce a bit from full and manually find tne correct height, i can't remember the exact number now, sorry

for me is this great app:
http://forum.xda-developers.com/showthread.php?t=414342

WAD2
For me the best is WAD2, even if still in RC12 and a little buggy.
However I've 9 virtual pages, a dozen of docks (used practically as other pages), full of graphical candy, everything at 2 taps, quite all the functionality many previous programs had, and the best it's very easy to do the interface YOU want!
All this never going under 16-18 Mb free on a 64 Mb Universal using Tomal 7.7 ROM. The counterpart to having all this RAM is page switching isn't the fastest. But if I had 128 RAM (can't find anybody in Italy!) I could get off the "low-memory" management and have the speed in change of more RAM.

IOS vs. Android - web page scrolling difference

If you used it side by side you'd know what I'm talking. IOS renders scrolling much, much smoother. When it detects a touch, it creates an Image of the page with resolution a bit higher than a screen. And then it moves it to fast image manipulation hw in gpu.
Cons against Android is you'll notice empty blocks of the page if you scrolled away than initial Image. iOS then creates additional Image from the browser. Cpu renders the image, gpu scrolls the Image.
Pros? It's smooth as a butter.
Can we make it optional on Android? I'm surprised how no one notices or talks about it.
Sent from my GT-I9000 using XDA App

This post was done based on Cyanogen/AOSP experience. Samsung stock ROM render scrolling similar to iPhone and it feels smoother.

A similar scenario:
I have a gallery of 1500+ photo's. On the iPhone 4 scrolling through the gallery is very smooth, like scrolling a single image (which it internally probably is). You can scroll back and forth at high speed without any visible delay or loading of thumbnails.
On my Nexus One and Sensation however you will see it load the thumbnails one by one. With small galleries you can go back and forth smoothy once all thumbs have been loaded into memory, which it does reasonably fast. The larger galleries however turn into a thumb loading fest when you're going back and forth at high speeds, making it much more tedious to find certain images.
I realize I can split up the gallery to avoid this issue. Just wanted to illustrate that the iPhone has a couple of tricks up it's sleeve which really aren't that complicated but may be worthwhile copying.

xnpu said:
A similar scenario:
I have a gallery of 1500+ photo's. On the iPhone 4 scrolling through the gallery is very smooth, like scrolling a single image (which it internally probably is). You can scroll back and forth at high speed without any visible delay or loading of thumbnails.
On my Nexus One and Sensation however you will see it load the thumbnails one by one. With small galleries you can go back and forth smoothy once all thumbs have been loaded into memory, which it does reasonably fast. The larger galleries however turn into a thumb loading fest when you're going back and forth at high speeds, making it much more tedious to find certain images.
I realize I can split up the gallery to avoid this issue. Just wanted to illustrate that the iPhone has a couple of tricks up it's sleeve which really aren't that complicated but may be worthwhile copying.
Click to expand...
Click to collapse
Thanks for bringing this issue. CM7 gallery on SGS is muuuuuch faster than stock 2.3.4. It flies like on iphone. Try it. For me browser is more important so I'll stick with stock.

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

[Q] Chrome: Doesn't seem to use 1920x1080 resolution?

I just noticed that when I view my website, Chrome doesn't seem to be using the full resolution of the tablet. Let me explain.
When I look at the 660x440 pixel images on my Desktop (Viewsonic VX2450, 1920x1080 resolution), these take up a relatively small portion of the screen, and I can see the entire image without scrolling. But when I view it on my Asus Infinity, which runs the same 1920x1080 resolution, the same 660x440 pixel image is much larger - the portrait orientated shots cannot be fully seen without scrolling, indicating that the vertical resolution is not 1080 pixels, for all practical purposes.
I have the "Desktop Requested" option selected, and I don't see any other settings to effect how Chrome displays its pages.
Am I missing something basic here, have something not set-up properly, or is this just the nature of the beast? FWIW, this works the same in the stock browser as well.

I feel the same way about chrome
try using different browsers
i think that the Maxthon browser is the best when it came to viewing images
they have a version made just for tablets

Same here with chrome.
I don't understand what's going on with it.
A lot of people rave about chrome.
Been using it trying figure out how it works.
Settings are minimal, web pages in Android won't zoom normally.
I agree about Maxthon or just about any other browser.
Features are much better in most other choices.
(*the TF700T has a resolution of 1920 by 1200)

I can't say I have noticed this myself by haven't tried a direct test. Have you tried looking at the browser settings for default zoom level? Possibly one or the other is displaying not at 100% zoom?

I appreciate the replies.
I have looked, but can't find any setting that would effect zoom or scaling, or something along those lines. Putting "chrome://chrome/settings/" into the address bar, which works on the desktop version of chrome, doesn't provide access in the android version ("this webpage is not available").
Guess I'll play around with some other browsers and see what I can find. I've heard/read good things about Boat and Dolphin; will have to check out Maxthon as well.
I just was curious about this, since it was unexpected - I would have assumed that the full 1920x1080 resolution would be taken advantage of by either the stock or the chrome browser, but apparently not...
Any other thoughts appreciated.

*note
The Infinity's res is 1920x1200
I know I know I'm a know it all

The other options I have just thought of is that I have not had a great deal of look with Chrome and requesting the desktop version of a website, even if you tick to get the desktop, I still get the mobile version. I mainly use the stock browser as you can default it to displaying desktop version (amongst other things). Or possibly, if you're using a different way of accessing the internet (wifi vs a 3G connection) the website may be delivering the content differently? I know that mobile operators in the UK used to scale down images/compress them over their connections, although I don't think they do this anymore. Just a thought...

DLCPhoto said:
When I look at the 660x440 pixel images on my Desktop (Viewsonic VX2450, 1920x1080 resolution), these take up a relatively small portion of the screen, and I can see the entire image without scrolling. But when I view it on my Asus Infinity, which runs the same 1920x1080 resolution, the same 660x440 pixel image is much larger
Click to expand...
Click to collapse
Switch your desktop OS to 240 dpi and then compare again. Browsers for high res screens usually zoom images because otherwise they would be far too tiny and out of proportion with the text.

_that said:
Switch your desktop OS to 240 dpi and then compare again. Browsers for high res screens usually zoom images because otherwise they would be far too tiny and out of proportion with the text.
Click to expand...
Click to collapse
Thanks for the reply.
Is it possible to change the DPI on a stock, unrooted Infinity tablet? I did a quick search and found LCD Density Modder that can do this, but it requires root. I can't find any 'conventional' settings on the device that will allow this.

DLCPhoto said:
Is it possible to change the DPI on a stock, unrooted Infinity tablet?
Click to expand...
Click to collapse
No, you need a custom kernel for that. Maybe it's possible to just find another browser where you can zoom out further.

DLCPhoto said:
Thanks for the reply.
Is it possible to change the DPI on a stock, unrooted Infinity tablet? I did a quick search and found LCD Density Modder that can do this, but it requires root. I can't find any 'conventional' settings on the device that will allow this.
Click to expand...
Click to collapse
You cannot change DPI on a fully stock TF700. Furthermore, although I can't find the reference at the moment, I have a vague memory of someone reporting in here after bricking their 700 with LDC Density Modder - I refrained from using it for that reason myself. (I haven't dared trying it, even with the Pro version I paid for for my SGS2... Sorry!)

_that said:
No, you need a custom kernel for that. Maybe it's possible to just find another browser where you can zoom out further.
Click to expand...
Click to collapse
Thanks.
I forgot to mention that I did try the Maxthon Browser - its settings do give you the option to change the default zoom (far, medium, close). But when I select "far" it does properly display whatever page I have open at less zoom, but then when I go to other pages, it reverts back to the usual medium setting (even though the settings menu itself still shows it on the "far" setting). So it's a poorly implemented, buggy feature, and I just uninstalled it. Haven't tried Boat or Dolphin yet.
It's not a huge issue, but it just hit me the other day that these browsers weren't scaling things properly, and I wanted to understand why, and what, if anything, I could do about it. Your comment about this being based on the dpi setting, rather than simple pixel resolution, makes a lot of sense.

Chrome just updated this morning.
Found the text scaling option\zoom, however the android browser still doesn't fit the tabs screen.
So chrome is still an ongoing PIA for this tablet at 1920x1200.......
Coming from the ground up

Thats OK said:
Chrome just updated this morning.
Found the text scaling option\zoom, however the android browser still doesn't fit the tabs screen.
So chrome is still an ongoing PIA for this tablet at 1920x1200.......
Coming from the ground up
Click to expand...
Click to collapse
Yeah, I saw the text scaling option, but the problem is how it handles graphics that's bugging me. It's bound to get better, right??

DLCPhoto said:
I forgot to mention that I did try the Maxthon Browser - its settings do give you the option to change the default zoom (far, medium, close).
Click to expand...
Click to collapse
The stock browser has the same setting - I tried them but could not really zoom out further.

I just noticed this the other day. Any updates on this subject?

[APP][3.0+][FREE] Super Touch 6.0.1

Here we present you the SUPER TOUCH -an android app to make your Android phone SUPER SMOOTH on Sliding, Zooming, List-scrolling.
FAQ: Please consider reading all the setup information when you open the app for the first time after installation
NOTE: This app is created and developed by Super Touch Developer I'm just creating op for him so any of its development work are not concerned with me...You can also mail your queries to [email protected]
App features:
1. Magnificent screen sliding respond, easy sliding on screen and no longer delay.
2. Incredibly smooth on zooming web pages or images as well as any operations needing to zoom.
3. Sliding to all directions is unbelievably quick and smooth.
4. Unbelievably quick and smooth lists rolling.
5. Much faster launching and loading Apps.
6. Speedy and accurate typing experience.
7. Much rapid on playing all sorts of games.
8. The first power-saving optimization app that does not affecting phones’ performance.
Super Touch allows you to experience unprecedented smooth smart phones.
Main functions：
One of this App’s main functions is to allow Android devices sliding much quicker and smoother, which will solve the problem of slow drag.
Sliding, dragging and zooming are far smoother; content follows up your fingertip; switching columns is also a lot quicker.
Lists rolling is extraordinarily speedier and smoother, typing is incredibly easier.
There is also a very practical power-saving optimization function, which doesn’t sacrifice the performance of the phone.
Screenshots:
Download:
Google play
Version Information:
Current Version: 6.0.1
compitable: android 3.0+ and supports both stock and custom ROMs
Thanks to Phone Arena for their app review
Thanks to Emily Wood for youtube video (watch it for test video)

I'm just asking some questions
How is using an app going to help with scrolling speed when it's after the device has been booted? Wouldn't that have to be started during bootup for it to be implemented at run time?
What files/libraries are being altered?

HasH_BrowN said:
I'm just asking some questions
How is using an app going to help with scrolling speed when it's after the device has been booted? Wouldn't that have to be started during bootup for it to be implemented at run time?
What files/libraries are being altered?
Click to expand...
Click to collapse
Every time the boot needs to be automatically optimized once and no modification of the system file..only docking system and touchscreen chip
thank you

After optimization, sliding is very smooth.

Seems to be many "helping" this dev by posting his app on XDA. But there is no need for multiple threads on the same app.
This one was first, http://forum.xda-developers.com/and...p-reduce-lag-make-touch-t3249927/post63847108
Thread closed, thanks!
Darth
Forum Moderator